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

**[Thomas Sauzedde](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tsauzedde)** opened **[MRELEASE-543](https://issues.apache.org/jira/browse/MRELEASE-543?redirect=false)** and commented

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.

---

**Affects:** 2.0

**Attachments:**
- [sample-projects.tgz](https://issues.apache.org/jira/secure/attachment/12718163/sample-projects.tgz) (_1.17 kB_)

**Issue Links:**
- [MRELEASE-294](https://issues.apache.org/jira/browse/MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.

- [MRELEASE-544](https://issues.apache.org/jira/browse/MRELEASE-544) prepare-with-pom : inherited plugins configuration are lost in release-pom.xml

5 votes, 6 watchers