IssueTracker

Hi, any update on this? Since this is still P3, I want to mention that this completely breaks publishing to maven central (so effectively most oss publishing) which requires artifacts to be signed. AGP is actively requesting users to switch to the API, which combined with the bug is not great

Thanks for the follow up, I am looking into it!

Same here. Maven Central doesn't accept javadoc without signature.

This is still an issue in 7.1.0-rc01 which still actively prompts you to use the new API

Thanks for your report! This bug is fixed and will be available in 7.2 beta02. Unfortunately it is too late for 7.1.

When publishing javadoc & sources with AGP 7.1, Gradle signing plugin will only sign one of the javadoc/sources artifacts of different build variants. (e.g. In your case, only app-1.0-debug-sources.jar is signed by Gradle signing plugin.)

Couldn't be it considered as a known 7.1 issue and included in any upcoming 7.1 patch? This API is effectively useless for Maven Central publishing which is probably the most popular use-case (or maybe that is not true).

Ivan, Jerome, our 7.1 PR_1 check in due date is Feb. 2, is it okay to include the fix for signing java doc/source jars?

The fix is cherry picked into 7.1 PR_1.

Thank you that helps a lot

Is 7.1.1 the mentioned 7.1 PR_1?

Yes, that is correct

Unfortunately I'm still seeing the issue in 7.1.1:

➜  MyApplication tree ~/.m2/repository/com/example/app/7.1.1
/Users/gabriel/.m2/repository/com/example/app/7.1.1
├── app-7.1.1-debug-javadoc.jar
├── app-7.1.1-debug-sources.jar
├── app-7.1.1-debug-sources.jar.asc
├── app-7.1.1-debug.aar
├── app-7.1.1-debug.aar.asc
├── app-7.1.1-release-javadoc.jar
├── app-7.1.1-release-sources.jar
├── app-7.1.1-release.aar
├── app-7.1.1-release.aar.asc
├── app-7.1.1.module
├── app-7.1.1.module.asc
├── app-7.1.1.pom
└── app-7.1.1.pom.asc
0 directories, 13 files

7.3.0-alpha01 is fine:

➜  MyApplication tree ~/.m2/repository/com/example/app/7.3.0-alpha01
/Users/gabriel/.m2/repository/com/example/app/7.3.0-alpha01
├── app-7.3.0-alpha01-debug-javadoc.jar
├── app-7.3.0-alpha01-debug-javadoc.jar.asc
├── app-7.3.0-alpha01-debug-sources.jar
├── app-7.3.0-alpha01-debug-sources.jar.asc
├── app-7.3.0-alpha01-debug.aar
├── app-7.3.0-alpha01-debug.aar.asc
├── app-7.3.0-alpha01-release-javadoc.jar
├── app-7.3.0-alpha01-release-javadoc.jar.asc
├── app-7.3.0-alpha01-release-sources.jar
├── app-7.3.0-alpha01-release-sources.jar.asc
├── app-7.3.0-alpha01-release.aar
├── app-7.3.0-alpha01-release.aar.asc
├── app-7.3.0-alpha01.module
├── app-7.3.0-alpha01.module.asc
├── app-7.3.0-alpha01.pom
└── app-7.3.0-alpha01.pom.asc

0 directories, 16 files

I couldn't test 7.2.0 because beta 2 isn't out yet.

I've attached 2 zips with the 7.1.1 and 7.3.0 projects that produced the output above by running ./gradlew publishToMavenLocal (they contain a test gpg key, so there is no additional configuration needed).

Thanks for sharing the sample projects and I got the same result as you. After checking with our release team, it turns out the fix is not included in 7.1.1 and it should be in 7.1.2. Could you twist your 7.1.1 project to update AGP version to 7.1.2 and see if that works? 7.1.2 should be available very soon.

Did this issue only affect Javadoc, and was it related to Gradle configuration cache?

@14 Can confirm that 7.1.2 works

Re #15, this issue is not related to configuration cache, please take a look of #6.

Re #16, thanks for testing it out and I am glad it works for you!