[GRADLE-1286] Unclear documentation on how to customize Maven POM Created: 04/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 1


When I try to customize the POM as shown below (taken from example 34.6 in the manual) and run the "install" task, none of the added information makes it into build/poms/pom-default.xml and the POM in the local Maven repo:

uploadArchives {
    repositories.mavenDeployer {
        pom.project {
            description "foo"
            // more customization goes here

Maybe I'd have to run the "deploy" task instead, but the manual doesn't say anything on this. After some research, I found that the following works:

install {
    repositories.mavenInstaller {
        pom.project {
            description "foo"
            // more customization goes here

Comment by Peter Niederwieser [ 04/Jan/11 ]

Should be: Maybe I'd have to run the "uploadArchives" task [...]

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 11:51:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.