[jira] (MRELEASE-543) prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml

["Sergei Ivanov (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342745#comment-342745 ] 

Sergei Ivanov commented on MRELEASE-543:
----------------------------------------

One more case for placing a wildcard exclusion on each top-level dependency. If project's dependencies use version ranges for transitive dependencies, this seems to be somehow affecting the version resolution for direct dependencies, even when the direct dependencies have fixed versions in the release POM. Using wildcard exclusions would ensure that only the specific fixed versions of direct dependencies were included into the project based on the release POM.

> 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 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 was sent by Atlassian JIRA
(v6.1.6#6162)