Android库Gradle发行版JAR

我怎样才能释放android-library项目的Jar包装?
我发现,classes.jar位于build/bundles/release/classes.jar ,我想这是正确的Jar包(包含*.class文件)。

有没有官方的方式,把图书馆发布成JAR而不是AAR?

编辑
我使用Gradle发布Maven构件,并且想要将JAR和AAR包一起发布。 所以JAR与签名,md5,清单,…
基于https://chris.banes.me/2013/08/27/pushing-aars-to-maven-central/

 apply plugin: 'maven' apply plugin: 'signing' configurations { archives { extendsFrom configurations.default } } def sonatypeRepositoryUrl if (isReleaseBuild()) { println 'RELEASE BUILD' sonatypeRepositoryUrl = "https://oss.sonatype.org/service/local/staging/deploy/maven2/" } else { println 'DEBUG BUILD' sonatypeRepositoryUrl = "https://oss.sonatype.org/content/repositories/snapshots/" } if(!hasProperty('nexusPassword')) { ext.set('nexusPassword', System.console().readPassword("\n\$ Type in password for Sonatype nexus account " + nexusUsername + ": ")) } if(!signing.hasProperty('password')) { ext.set('signing.password', System.console().readPassword("\n\$ Type in GPG key password: ")) } afterEvaluate { project -> uploadArchives { repositories { mavenDeployer { beforeDeployment { MavenDeployment deployment -> signing.signPom(deployment) } pom.artifactId = POM_ARTIFACT_ID repository(url: sonatypeRepositoryUrl) { authentication(userName: nexusUsername, password: nexusPassword) } pom.project { name POM_NAME packaging POM_PACKAGING description POM_DESCRIPTION url POM_URL scm { url POM_SCM_URL connection POM_SCM_CONNECTION developerConnection POM_SCM_DEV_CONNECTION } licenses { license { name POM_LICENCE_NAME url POM_LICENCE_URL distribution POM_LICENCE_DIST } } developers { developer { id "loopj" name "James Smith" } developer { id "smarek" name "Marek Sebera" } } } } } } signing { required { isReleaseBuild() && gradle.taskGraph.hasTask("uploadArchives") } sign configurations.archives } task androidJavadocs(type: Javadoc) { source = android.sourceSets.main.java.srcDirs } task androidJavadocsJar(type: Jar) { classifier = 'javadoc' from androidJavadocs.destinationDir } task androidSourcesJar(type: Jar) { classifier = 'sources' from android.sourceSets.main.java.srcDirs } artifacts { archives androidSourcesJar archives androidJavadocsJar } } 

运用

 task androidJar(type: Jar) { from android.sourceSets.main.java.srcDirs } 

将只打包java文件,而不是编译和链接到android sdk

虽然我还没有尝试通过部署到Sonatype(甚至是本地回购)上传工件,但这是几周前我试图解决相同问题时想出的。

 android.libraryVariants.all { variant -> def name = variant.buildType.name if (name.equals(com.android.builder.core.BuilderConstants.DEBUG)) { return; // Skip debug builds. } def task = project.tasks.create "jar${name.capitalize()}", Jar task.dependsOn variant.javaCompile task.from variant.javaCompile.destinationDir artifacts.add('archives', task); } 

然后运行以下内容:

 ./gradlew jarRelease 

通过Gradle从库项目生成jar的另一种方法如下:

在你的图书馆的build.gradle:

 def jarName = 'someJarName.jar' task clearJar(type: Delete) { delete "${project.buildDir}/libs/" + jarName } task makeJar(type: Copy) { from("${project.buildDir}/intermediates/bundles/release/") into("${project.buildDir}/libs/") include('classes.jar') rename('classes.jar', jarName) } makeJar.dependsOn(clearJar, build) 

我们在这里做的只是复制由Android Gradle插件生成的classes.jar。 一定要查看你的构build目录中的这个文件,看看它的内容是否在你想要的方式。

然后运行makeJar任务,生成的jar将在库/ build / libs / ${jarName} .jar中

将根据您的configuration发布类文件。 如果您正在对其进行混淆,则jar中的文件将被混淆。

只是因为以前的答案不符合我的需求,我分享我的棘手版本生成与项目类和aar / jar依赖关系的jar。

 // A tricky jar operation, we want to generate a jar files that contains only the required classes used. // Dependencies are in jar and aar, so we need to open the aar to extract the classes and put all at the same level // (aar is a zip that contains classes.jar, the latter is a zip that contains .class files) task jar(type: Jar) { from { List<File> allFiles = new ArrayList<>(); configurations.compile.collect { for (File f : zipTree(it).getFiles()) { if (f.getName().equals("classes.jar")) { allFiles.addAll(zipTree(f).getAt("asFileTrees").get(0).getDir()) } } } allFiles.add(new File('build/intermediates/classes/release')) allFiles // To return the result inside a lambda } archiveName( project.ext.appName + '.jar' ) } 

这不会pipe理构buildtypes/风味,但可以适应(build立在没有味道的构buildtypes发布上就可以)。

如果你有更聪明或更优雅的解决scheme,请分享!