我面临同样的挑战，这里是最好的，我可以让尚未：
使用mavenPublications和沿bintray插件gradle这个maven-publish插件，你可以发布任何变种mavenLocal和bintray。
这里的publish.gradle文件我申请我所有的项目库模块的最后，我要发布：
def pomConfig = {
licenses {
license {
name 'The Apache Software License, Version 2.0'
url 'http://www.apache.org/licenses/LICENSE-2.0.txt'
}
}
developers {
developer {
id 'louiscad'
name 'Louis CAD'
email '[email protected]'
}
}
scm {
connection 'https://github.com/LouisCAD/Splitties.git'
developerConnection 'https://github.com/LouisCAD/Splitties.git'
url siteUrl
}
}
def publicationNames = []
publishing.publications {
android.libraryVariants.all { variant ->
if (variant.buildType.name == "debug") return // Prevents publishing debug library
def flavored = !variant.flavorName.isEmpty()
/**
* Translates "_" in flavor names to "-" for artifactIds, because "-" in flavor name is an
* illegal character, but is well used in artifactId names.
*/
def variantArtifactId = flavored ? variant.flavorName.replace('_', '-') : project.name
/**
* If the javadoc destinationDir wasn't changed per flavor, the libraryVariants would
* overwrite the javaDoc as all variants would write in the same directory
* before the last javadoc jar would have been built, which would cause the last javadoc
* jar to include classes from other flavors that it doesn't include.
*
* Yes, tricky.
*
* Note that "${buildDir}/docs/javadoc" is the default javadoc destinationDir.
*/
def javaDocDestDir = file("${buildDir}/docs/javadoc ${flavored ? variantArtifactId : ""}")
/**
* Includes
*/
def sourceDirs = variant.sourceSets.collect {
it.javaDirectories // Also includes kotlin sources if any.
}
def javadoc = task("${variant.name}Javadoc", type: Javadoc) {
description "Generates Javadoc for ${variant.name}."
source = variant.javaCompile.source // Yes, javaCompile is deprecated,
// but I didn't find any working alternative. Please, tweet @Louis_CAD if you find one.
destinationDir = javaDocDestDir
classpath += files(android.getBootClasspath().join(File.pathSeparator))
classpath += files(configurations.compile)
options.links("http://docs.oracle.com/javase/7/docs/api/");
options.links("http://d.android.com/reference/");
exclude '**/BuildConfig.java'
exclude '**/R.java'
failOnError false
}
def javadocJar = task("${variant.name}JavadocJar", type: Jar, dependsOn: javadoc) {
description "Puts Javadoc for ${variant.name} in a jar."
classifier = 'javadoc'
from javadoc.destinationDir
}
def sourcesJar = task("${variant.name}SourcesJar", type: Jar) {
description "Puts sources for ${variant.name} in a jar."
from sourceDirs
classifier = 'sources'
}
def publicationName = "splitties${variant.name.capitalize()}Library"
publicationNames.add(publicationName)
"$publicationName"(MavenPublication) {
artifactId variantArtifactId
group groupId
version libraryVersion
artifact variant.outputs[0].packageLibrary // This is the aar library
artifact sourcesJar
artifact javadocJar
pom {
packaging 'aar'
withXml {
def root = asNode()
root.appendNode("name", 'Splitties')
root.appendNode("url", siteUrl)
root.children().last() + pomConfig
def depsNode = root["dependencies"][0] ?: root.appendNode("dependencies")
def addDep = {
if (it.group == null) return // Avoid empty dependency nodes
def dependencyNode = depsNode.appendNode('dependency')
dependencyNode.appendNode('groupId', it.group)
dependencyNode.appendNode('artifactId', it.name)
dependencyNode.appendNode('version', it.version)
if (it.hasProperty('optional') && it.optional) {
dependencyNode.appendNode('optional', 'true')
}
}
// Add deps that everyone has
configurations.compile.allDependencies.each addDep
// Add flavor specific deps
if (flavored) {
configurations["${variant.flavorName}Compile"].allDependencies.each addDep
}
// NOTE: This library doesn't use builtTypes specific dependencies, so no need to add them.
}
}
}
}
}
group = groupId
version = libraryVersion
afterEvaluate {
bintray {
user = bintray_user
key = bintray_api_key
publications = publicationNames
override = true
pkg {
repo = 'splitties'
name = project.name
desc = libraryDesc
websiteUrl = siteUrl
issueTrackerUrl = 'https://github.com/LouisCAD/Splitties/issues'
vcsUrl = gitUrl
licenses = ['Apache-2.0']
labels = ['aar', 'android']
publicDownloadNumbers = true
githubRepo = 'LouisCAD/Splitties'
}
}
}
为了这个工作，我需要有定义的bintray_user和bintray_api_key性能。我个人只是有他们在我的~/.gradle/gradle.properties文件是这样的：
bintray_user=my_bintray_user_name
bintray_api_key=my_private_bintray_api_key
我还需要定义我在publish.gradle文件中使用我的根项目的build.gradle文件中的以下扩展属性：
allprojects {
...
ext {
...
// Libraries
groupId = "xyz.louiscad.splitties"
libraryVersion = "1.2.1"
siteUrl = 'https://github.com/LouisCAD/Splitties'
gitUrl = 'https://github.com/LouisCAD/Splitties.git'
}
}
现在，我终于可以在我的android库模块中使用它，我有多个productFlavors。下面是一个发布的库模块的build.gradle文件的一个片段：
plugins {
id "com.jfrog.bintray" version "1.7.3" // Enables publishing to bintray
id "com.github.dcendents.android-maven" version "1.5" // Allows aar in mavenPublications
}
apply plugin: 'com.android.library'
apply plugin: 'maven-publish' // Used for mavenPublications
android {
...
defaultPublishConfig "myLibraryDebug" // Allows using this library in another
// module in this project without publishing to mavenLocal or Bintray.
// Useful for debug purposes, or for your library's sample app.
defaultConfig {
...
versionName libraryVersion
...
}
...
productFlavors {
myLibrary
myLibrary_logged // Here, the "_" will be replaced "-" in artifactId when publishing.
myOtherLibraryFlavor
}
...
}
dependencies {
...
// Timber, a log utility.
myLibrary_loggedCompile "com.jakewharton.timber:timber:${timberVersion}"; // Just an example
}
...
ext {
libraryDesc = "Delegates for kotlin on android that check UI thread"
}
apply from: '../publish.gradle' // Makes this library publishable
当你拥有所有这些设置不当，你的库的名称，而不是mine's（你可以作为一个例子使用），你可以尝试发布试图首先发布到mavenLocal的风格库的一个版本。 要做到这一点，运行这个命令：
myLibrary $ ../gradlew publishToMavenLocal
然后，您可以尝试添加在你的应用程序的库(example here)mavenLocal，然后尝试在你的库作为依赖（artifactId的应该是味道的名字，用“_”代替“ - “）并构建它。 您也可以使用文件资源管理器（在Finder的Mac上使用cmd + shift + G访问隐藏文件夹）检查目录~/.m2并查找您的资料库。
当它的时间发布到bintray/jcenter，你只需要运行这个命令：您发布库mavenLocal，Bintray或其他Maven仓库之前
：
myLibrary $ ../gradlew bintrayUpload
重要，您通常会想要使用该库的示例应用程序试用您的库。此示例应用程序应该是同一项目中的另一个模块，只需要具有项目依赖关系，该应用程序应该如下所示：compile project(':myLibrary')。但是，由于您的图书馆有多个productFlavors，因此您需要测试所有这些。不幸的是，目前不可能从样例应用程序的build.gradle文件中指定要使用的配置（除非您在库的build.gradle文件中使用publishNonDefault true，这会打破maven和bintray出版物），但您可以指定默认配置（即buildVariant）在你图书馆的模块中：defaultPublishConfig "myLibraryDebug"在android关闭。您可以在Android Studio的“Build Variants”工具窗口中查看库的可用构建变体。
随意探索my library "Splitties" here如果你需要一个例子。有味的模块名为concurrency，但我也使用我的脚本处理无味的库模块，我在项目中的所有库模块上进行了全面测试。
如果您需要帮助为您设置，您可以联系我。
你必须更新每个风味不同的神器。 –
@GabrieleMariotti你怎么能在bintray'配置'中指定味道？ –
我没有尝试过。但是你必须指定flavor块中的某些部分的bintray配置来分配工件名称。 –