[MSHADE-95] test-scoped artifact excluded, even if it is also a transitive dep

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.3.2, 1.4
• Labels: moreinfo

Environment

(cygwin)

Apache Maven 3.0.1 (r1038046; 2010-11-23 05:58:32-0500)
Java version: 1.6.0_23
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"

• Assignee: Unassigned
• Reporter: Alan D. Salewski
• Created: 10/Mar/11 12:29
• Updated: 18/Dec/19 12:01
• Resolved: 18/Dec/19 12:01

Description

A test-scoped artifact is excluded from the final jar, even if that artifact is also a transitive dependency of some other (non-test-scoped) dep.

MY_POM
  |
  |
  +-- dep A (scope: test)
  |
  |
  +-- dep B (scope: compile)
        |
        |
        +-- dep A (scope: compile)

In the above scenario, I would expect 'dep A' to be included in the final jar, even though it's in the 'test' scope in my POM. The rationale is that it is required for 'dep B' to run; its absence will result in a java.lang.ClassNotFoundException at runtime.

Behavior observed with maven-shade-plugin versions 1.3.2 and 1.4; other versions not tested.

I'll put together a test case later tonight when I have more time and attach it here.

Issue Links

• is duplicated by: MSHADE-110 a local "test" dependency causes that to not be included in the shaded jar, even if it probably should be.
• relates to: MRELEASE-140 Tests fail during release:perform but work elsewhere