Android Library Gradle发布JAR

Mar*_*era 64 java android jar gradle aar

如何发布android-library项目的Jar包装?
我发现,classes.jar位于下面build/bundles/release/classes.jar,我想这是正确的Jar包(包含*.class文件).

是否有一些官方的方式,将库作为​​JAR而不是AAR发布?

编辑
我使用Gradle来发布Maven工件,我想发布JAR和AAR包.所以带有签名的JAR,md5,manifest,......
基于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
    }
}
Run Code Online (Sandbox Code Playgroud)

运用

task androidJar(type: Jar) {
    from android.sourceSets.main.java.srcDirs
}
Run Code Online (Sandbox Code Playgroud)

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

Jak*_*ton 93

虽然我没有尝试将部署的工件上传到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);
}
Run Code Online (Sandbox Code Playgroud)

然后运行以下命令:

./gradlew jarRelease
Run Code Online (Sandbox Code Playgroud)

  • 谢谢这确实有帮助,但它仍然不会生成依赖项的类文件.我正在尝试制作一个SDK jar,基本上是一个传递出来的jar,但是这个编译不包括它所依赖的模块项目,也不会从依赖部分等下拉jar.你有没有建议实现这一点,它将库项目编译到jar中,所以我不需要分发4个罐子,每个库项目一个.那么很好地弄清楚如何像Gson或Otto那样包含maven依赖罐. (6认同)
  • 我也可以确认这是有效的.请注意,运行**`gradle tasks`**时,生成的任务不会显示,只能使用**`gradle tasks --all`**.再次感谢! (4认同)
  • 知道如何让它与proguard一起工作吗? (3认同)
  • 有人可以指出我如何使用此配置的proguard?似乎使用proguard定义buildTypes不适用. (2认同)
  • @Kevin,我用"jar $ {variant.name.capitalize()}"`交换了``jar $ {name.capitalize()}``part,以便为任务名称创建任务帐户(`变体' .name`由buildType name和productFlavor名称组成) (2认同)