[
https://jira.codehaus.org/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308943#comment-308943
]
Bartosz Radaczynski commented on MRELEASE-543:
----------------------------------------------
Does this also impact transitive exclusions or just inherited ones?
> prepare-with-pom : inherited dependencies exclusion are lost in
> release-pom.xml
> -------------------------------------------------------------------------------
>
> Key: MRELEASE-543
> URL: https://jira.codehaus.org/browse/MRELEASE-543
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare-with-pom
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Thomas Sauzedde
> Attachments: sample-projects.tgz
>
>
> 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 my exclusions
> defined in "grandfather" are 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
> You will see that in your tagged release-pom.xml the exclusions are lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
