[
http://jira.codehaus.org/browse/MRELEASE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Clark updated MRELEASE-438:
----------------------------------
Attachment: parent-artifact-2.pom
parent-artifact-1.pom
pom.xml
parent-artifact.pom
This is a simple parent pom which has maven-antrun-plugin configured in
project/build/pluginManagement to be inherited in verify phase by child
projects.
This project was released with mvn 2.0.10 using the
maven-release-plugin-2.0-beta-8, the resultant pom is attached as
parent-artifact-1.pom.
This project was released again with mvn 2.0.9 using the
maven-release-plugin-2.0-beta-7, the resultant pom is parent-artifact-2.pom
> A parent pom's "build.pluginManagement" plugin configuration is stripped from
> released pom and can't be inherited.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-438
> URL: http://jira.codehaus.org/browse/MRELEASE-438
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Windows XP SP3, JSDK 1.6.0_12
> Reporter: Robert Clark
> Attachments: parent-artifact-1.pom, parent-artifact-2.pom, pom.xml
>
>
> This behaviour is apparent in 2.0.10 and 2.1.0, but when I rolled back to
> 2.0.9 it worked as intended.
> Start with a parent pom of packaging "pom". In the <build> section, add a
> <pluginManagement> section containing anything (I tried a simple
> maven-antrun-plugin to echo something in verify phase, but anything will do).
> Ensure the project containing this pom is under source control. Perform a
> release:prepare and release:perform, NOT of snapshot versions. At this stage
> you can see the released pom doesn't have the pluginManagement section as it
> should.
> Create a child project whose parent is the released parent as above. Add the
> appropriate plugin identifier to the build section so that pluginManagement
> above is pulled in. Execute "mvn help:effective-pom" to see that no
> configuration is found.
> This bug doesn't become apparent until releasing, as SNAPSHOT poms don't have
> the pluginManagement stripped.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
