[MSHADE-311] Bad exclusions in dependency-reduced-pom.xml

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 3.2.1
• Fix Version/s: 3.2.2
• Environment: maven-shade-plugin 3.2.1 ; Maven 3.6.0 ; JDK 11
• Assignee: Karl Heinz Marbaise
• Reporter: Dmitri Gabbasov
• Created: 30/Jan/19 23:09
• Updated: 04/Jan/20 20:43
• Resolved: 04/Jan/20 20:34

Description

Given the following dependency graph:

test:foo:jar:1.0.0-SNAPSHOT
+- test:foz:jar:1.0.0-SNAPSHOT:compile
\- test:bar:jar:1.0.0-SNAPSHOT:provided
   \- test:baz:jar:1.0.0-SNAPSHOT:provided

where baz is a compile scope dependency of bar (and therefore a provided scope dependency of foo). And given the following maven-shade-plugin configuration in foo:

<configuration>
  <artifactSet>
    <includes>
      <include>test:foz</include>
    </includes>
  </artifactSet>
</configuration>

A weird dependency-reduced-pom.xml file is produced for foo, where the bar dependency declaration gets an exclusion for baz:

<dependencies>
  <dependency>
    <groupId>test</groupId>
    <artifactId>bar</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <scope>provided</scope>
    <exclusions>
      <exclusion>
        <artifactId>baz</artifactId>
        <groupId>test</groupId>
      </exclusion>
    </exclusions>
  </dependency>
</dependencies>

Such an exclusion is unexpected and seems wrong to me.

Issue Links

• links to: GitHub Pull Request #35