Open sdavids opened 6 years ago
I came up with the following workaround:
bintray {
// ...
publications = ['mavenJava']
filesSpec {
from("${buildDir}/libs") {
include '*.jar.asc'
}
from("${buildDir}/publications/mavenJava") {
include 'pom-default.xml.asc'
rename 'pom-default.xml.asc', "${project.name}-${project.version}.pom.asc"
}
into "${project.group.replaceAll(/\./, '/')}/${project.name}/${project.version}"
}
pkg {
// ...
}
}
But this should be handled by the plugin by default ...
@sdavids hello. Do you have solving of this problem?
Had the same problem, ended up removing gradle-bintray-plugin completely and just using this instead:
publishing {
repositories {
maven {
name = 'bintray'
url = 'https://api.bintray.com/maven/<owner>/<repo>/<pkg>/;publish=1'
credentials {
username = System.env['BINTRAY_USER']
password = System.env['BINTRAY_KEY']
}
}
}
}
Setup:
./gradlew clean publishToMavenLocal
will place the 3 JARs, the POM, and the 4 signature files (*.asc) into the local maven repository—which is correct../gradlew clean bintrayUpload
will place the 3 JARs, the POM, and the 4 signature files (*.asc) into the local maven repository (publishToMavenLocal called implicitly), but only upload the 3 JARs and the POM to bintray—which is incorrect.