Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
2.0
-
None
-
None
-
Maven 2.2.1
Description
Like in the provided sample projects, I have the following scenario : 3 modules (sibling) with the following inheritage graph :
grandfather <=== father <=== child
- grandfather (pom module) has
- a dependencyManagement block with some exclusions
- a pluginManagement block
- father (pom module) adds a plugins block to configure the compiler plugin
- child is a basic (empty) jar module
when mvn release:prepare-with-pom is performed on "child" the checked-in (svn) release-pom.xml has all the dependencies resolved BUT all the inherited plugins configuration is lost
To reproduce this with the provided sample projects :
- perform a mvn:install on grandfather & father
- import "child" in your svn repo
- change the scm block on "child" in order to checkout/in from your svn
- perform a mvn release:prepare-with-pom (on child)
You will see that in your tagged release-pom.xml the plugins configuration is lost.
Attachments
Attachments
Issue Links
- relates to
-
MRELEASE-294 Generated release-pom.xml does not contain plugins configured in a super pom.
- Open
-
MRELEASE-543 prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml
- Open