[GRADLE-3285] Publish plugin should either allow uploading of signature files or downgrade error to a warning Created: 19/Apr/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Tom Dunstan Assignee: Unassigned
Resolution: Won't Fix Votes: 2


From the forums "Gradle publish-plugin fails if the artifacts are signed":

"Gradle publish-plugin fails to publish if the artefacts in the project are signed. The signing plugin generates GPG signatures for all artefacts with an asc extension, which causes the publish plugin to fail.

"It would be preferable to issue a warning and ignore any unknown artefacts instead of failing, so that plugins can still be published to the plugin portal."


We should either allow uploading of these files or downgrade the error to a warning - they're very common.

Comment by Ben Bader [ 07/Jun/15 ]

Ping! I'd love to publish my plugin, but currently it's not worth the work - we already distribute via Maven Central which requires signing, and it seems quite involved to disable signing just for plugins.gradle.org publishing.


Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:44:49 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.