[GRADLE-1589] Name the POM artifact in the Gradle build by what it will be published as Created: 04/Jun/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
When pom files are published, they are published as «artifact-name»-«version».pom. Internally in Gradle, this artifact is modelled with a name of pom-default.xml.
This causes problems for things like the signing plugin that need to create a signature file based on to-be-published artifacts like the POM. At build time, the name of the POM is different to the name it will be published as. Artifacts such as jars don't suffer from this. This means that you need to put in special handling for POM artifacts which is error prone.
|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.