[GRADLE-841] MavenPom - Enhance to allow for more pom elements to be set Created: 04/Mar/10 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: | Shay Banon | Assignee: | Hans Dockter |
| Resolution: | Fixed | Votes: | 1 |
| Issue Links: |
|
||||||||
| Description |
|
MavenPom now has several properties that can be set to control the pom file. It would be nice to add more properties that allow to set the "required" fields listed here: http://nexus.sonatype.org/oss-repository-hosting.html#4. |
| Comments |
| Comment by Hans Dockter [ 04/Mar/10 ] |
|
You can set all those properties via pom.mavenProject, which gives you access to a native org.apache.maven.project.MavenProject object. This allows you to sett everything. This object comes from the maven ant tasks jar shipped with Gradle. Furthermore you can even hook into the actual generated pom.xml to read/modify it. All properties of the Gradle pom object delegate to the MavenProject class. It is a bit arbitrary for which Maven properties we provide delegate methods and for which not. The document you are referring to is a good guideline for the stuff we should provide convenience delegate methods for. Have a look at the Javadoc of the Gradle MavenPom interface. |
| Comment by Steve Ebersole [ 05/Mar/10 ] |
|
i cannot link... but related to http://jira.codehaus.org/browse/GRADLE-290 |