[GRADLE-3183] Cannot sign artifacts when using maven-publish plugin Created: 20/Oct/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I am working on replacing a Maven build with Gradle where one of the requirements is to publish to Maven Central. I thus need to sign not only the artifacts but also the pom file. I started using the maven-publish plugin as it seemed to be the reasonable choice for a new project, but now I have run into the obstacle that it seems impossible to sign the pom file with the new plugin.

I have been reading docs and googling for a while, and all answers to this problem seem rather old. I could not find any related issues in the Gradle issue database. Before I switch to the old, dying maven-plugin, I wanted to make sure that I have not misunderstood: is it still impossible to sign the pom file with the new maven-publish plugin?

Comment by Gradle Forums [ 20/Oct/14 ]

As far as I know, it's still impossible. One alternative is to publish to Maven Central via jCenter, which does the signing for you.

Comment by Gradle Forums [ 20/Oct/14 ]

Thank you for your reply Peter. I find this quite unfortunate: as the old maven plugin is left dying slowly, more and more people will, like me, be trapped in an impossible situation if the new plugin is not feature complete. For me, it's impossible right now to change my organization's deploy routines, and go the jCenter way. This project was an attempt to show case the superiority of Gradle over Maven, but now I see no easy way forward.

I am surprised there's not even issue on this, or was my search in the issue database incomplete?

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:42:10 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.