You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 11:28:00 UTC
[jira] [Updated] (MRELEASE-543) prepare-with-pom : inherited
dependencies exclusion are lost in release-pom.xml
[ https://issues.apache.org/jira/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold updated MRELEASE-543:
-------------------------------------------
Labels: needs-attention (was: )
> prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml
> -------------------------------------------------------------------------------
>
> Key: MRELEASE-543
> URL: https://issues.apache.org/jira/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
> Priority: Major
> Labels: needs-attention
> 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
(v8.3.4#803005)