[GRADLE-290] Allow customization of generated Pom Created: 30/Oct/08  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9-rc-1

Type: Improvement
Reporter: Hans Dockter Assignee: Hans Dockter
Resolution: Fixed Votes: 1

Issue Links:
Duplicated by GRADLE-841 MavenPom - Enhance to allow for more ... Resolved


Allow to modify auto-created dependencies.
Allow to remove auto-create dependencies.
Allow to add manually created dependencies.

Comment by Jon Cox [ 23/Jan/09 ]

If new features are added to support Ivy's "override" feature, it would be nice
if the customization mechanism worked with that too.

See also: GRADLE-244

Comment by Hans Dockter [ 26/Jan/09 ]


Comment by Steve Ebersole [ 07/Nov/09 ]

Is this the right place to note the desired ability to specify other pom metadata? My understand is that you can only effect stuff into the generated pom based on what is available in http://www.gradle.org/latest/docs/javadoc/org/gradle/api/artifacts/maven/MavenPom.html I apologize if that is not correct understanding.

Or should this go in a separate issue?

Specifically we had talked about:

  • <url/>
  • <organization/>
  • <licenses/> (MavenPom does have something called "LicenseHeader", just not sure what it is)
  • <scm/>
  • <issueManagement/>

Nice to haves:

  • <developers/> - mainly because it generally defines copyright
  • <ciManagement/>
Comment by Hans Dockter [ 10/Nov/09 ]

This is the right issue. Gradle needs to provide a MavenPom object with entries for all that. As a last fall back we will also provide an access to the XML object (e.g. in the case a Maven trunk version offers a new element which is not part of the Gradle Pom object).

Generated at Wed Jun 30 11:26:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.