[MSHADE-202] When promoteTransitiveDependencies=true, some <exclusions> are stripped from the dependency-reduced-pom

**[Andrey Stepaonv](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=drutech)** opened **[MSHADE-202](https://issues.apache.org/jira/browse/MSHADE-202?redirect=false)** and commented

I have 2 modules. First module uses this dependencies:

```xml

ch.imvs
sdes4j
1.1.3


commons-codec
commons-codec

commons-codec
commons-codec
1.10

```

and second module uses first module and maven-shade plugin with execution:

```xml

shade-for-obfuscate
package

shade

${project.groupId}:firstModule


true
${basedir}/target/dependency-reduced-pom.xml

```

As a result i have reduced pom with dependencies:

```xml

ch.imvs
sdes4j
1.1.3
compile

commons-codec
commons-codec
1.10
compile

```

But i had to get dependency with \

---

**Affects:** 2.4.1

**Issue Links:**
- [MSHARED-852](https://issues.apache.org/jira/browse/MSHARED-852) Add Exclusions to DependencyNode
(_**"depends upon"**_)

1 votes, 3 watchers

Start with the maven-shade plugin's promoteTransitiveDependencies handling and reproduce the issue using the two-module configuration and dependency-reduced-pom.xml described in the report. Trace how dependency exclusions are represented while transitive dependencies are promoted; done means the reduced POM retains the commons-codec exclusion from sdes4j.

Written by the indexing model from the issue text.