[MNG-4526] [regression] Shade plugin includes too much (relative to 2.2.1)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-6
• Fix Version/s: 3.0-alpha-7
• Component/s: Plugins and Lifecycle
• Environment: OS X 10.5.8
• Assignee: Benjamin Bentmann
• Reporter: Dominic Mitchell
• Created: 10/Jan/10 15:21
• Updated: 01/Jun/21 06:38
• Resolved: 28/Jan/10 17:50

Description

When creating a shaded jar using the maven 3.0-alpha-6, I get too many dependencies included. I think it's incorrectly including things in provided scope.

My project is jslint4java. This is what I see when I run mvn -Pdist clean package:

[INFO] --- maven-shade-plugin:1.2.2:shade (make-shaded-jar) @ jslint4java-ant ---
[INFO] Including com.googlecode.jslint4java:jslint4java:jar:1.3.4-SNAPSHOT in the shaded jar.
[INFO] Including rhino:js:jar:1.7R1 in the shaded jar.
[INFO] Including org.apache.ant:ant:jar:1.7.1 in the shaded jar.
[INFO] Including org.apache.ant:ant-launcher:jar:1.7.1 in the shaded jar.
[INFO] Including org.apache.ant:ant-antunit:jar:1.1 in the shaded jar.
[INFO] Including junit:junit:jar:4.6 in the shaded jar.
[INFO] Attaching shaded artifact.

Of those dependencies, only the first two should be included. This worked correctly in maven-2.2.1.

Unfortunately, I've no idea what's going wrong — whether it's the shade plugin or something in core maven. I've attached a zip of the source, as well as mvn -X output for both 3.0-alpha-6 and 2.2.1.

Issue Links

• causes: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath
• is related to: MNG-3297 maven should not give dependencies to plugins that don't @requireDependencyResolution
• relates to: MEJB-46 classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7