You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Clark (JIRA)" <ji...@codehaus.org> on 2009/04/08 10:41:23 UTC
[jira] Created: (MNG-4125) A parent pom's "build.pluginManagement"
plugin configuration is stripped from released pom and can't be inherited.
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.1.0, 2.0.10
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
[jira] Commented: (MRELEASE-438) A parent pom's
"build.pluginManagement" plugin configuration is stripped from released pom
and can't be inherited.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172609#action_172609 ]
Benjamin Bentmann commented on MRELEASE-438:
--------------------------------------------
Can you attach example parent POMs, one being good and the other being broken, such that we have a clear image of the defect?
> 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
>
> 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
[jira] Moved: (MRELEASE-438) A parent pom's
"build.pluginManagement" plugin configuration is stripped from released pom
and can't be inherited.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4125 to MRELEASE-438:
-------------------------------------------------
Affects Version/s: (was: 2.1.0)
(was: 2.0.10)
2.0-beta-8
Component/s: (was: Deployment)
prepare
Complexity: (was: Intermediate)
Key: MRELEASE-438 (was: MNG-4125)
Project: Maven 2.x Release Plugin (was: Maven 2)
> 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
>
> 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
[jira] Updated: (MRELEASE-438) A parent pom's
"build.pluginManagement" plugin configuration is stripped from released pom
and can't be inherited.
Posted by "Robert Clark (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4125) A parent pom's
"build.pluginManagement" plugin configuration is stripped from released pom
and can't be inherited.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172581#action_172581 ]
Benjamin Bentmann commented on MNG-4125:
----------------------------------------
What exactly do you mean by "released pom"? Do you refer to the parameter generateReleasePoms of the Maven Release Plugin?
The super POM of Maven 2.0.9 declares maven-release-plugin:2.0-beta-7 while newer Maven versions default to maven-release-plugin:2.0-beta-8. Can you verify that switching the Maven versions does not result in usage of different versions of the Release Plugin? Otherwise, this looks more like an issue with the Maven Release Plugin than with the Maven core itself.
> 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
[jira] Commented: (MNG-4125) A parent pom's
"build.pluginManagement" plugin configuration is stripped from released pom
and can't be inherited.
Posted by "Robert Clark (JIRA)" <ji...@codehaus.org>.
[ 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