[GRADLE-1035] Provide a 'maven central' plugin to ease deployment of artifacts and ensure well-formed poms Created: 15/Jul/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Chris Beams | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 13 |
| Issue Links: |
|
||||||||
| Description |
|
Sonatype requires certain elements in the POM when deploying to Maven Central. See https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement Adding to the DSL the capability to declare licensing information would be useful. Anything that avoids pom customization for typical cases is the idea here. There's also business in the document about using PGP keys, and I'm not certain that Gradle has support for this. |
| Comments |
| 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:
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. |