[ 
http://jira.codehaus.org/browse/MNG-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172585#action_172585
 ] 

Robert Clark commented on MNG-4125:
-----------------------------------

By "released pom" I meant the pom that ends up being the parent pom artifact in 
the release repository.  This is not to do with the generateReleasePoms 
parameter.

Thanks for the maven-release-plugin hint.  Yes, maven 2.0.10 uses 
maven-release-plugin:2.0-beta-8.  When I configured 2.0.10 to use 2.0-beta-7 
the problem went away and the pluginManagement section is preserved in the 
released parent pom.

Please advise whether I should raise the issue against that plugin or will you 
administer that.

> A parent pom's "build.pluginManagement" plugin configuration is stripped from 
> released pom and can't be inherited.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4125
>                 URL: http://jira.codehaus.org/browse/MNG-4125
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 2.0.10, 2.1.0
>         Environment: Windows XP SP3, JSDK 1.6.0_12
>            Reporter: Robert Clark
>
> 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

        

Reply via email to