[
https://issues.apache.org/jira/browse/MSHADE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802745#comment-14802745
]
Ilia commented on MSHADE-95:
----------------------------
I have the same issue with shade plugin version 2.4.1 and Maven 3.3.3 (JDK
8u40). IMHO, it is quite critical issue and I do not understand why it was not
fixed during last 4 years. Any ideas?
> test-scoped artifact excluded, even if it is also a transitive dep
> ------------------------------------------------------------------
>
> Key: MSHADE-95
> URL: https://issues.apache.org/jira/browse/MSHADE-95
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.4
> 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"
> Reporter: Alan D. Salewski
> Labels: moreinfo
> Attachments: MSHADE-95-IT.patch
>
>
> 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.
> {noformat}
> MY_POM
> |
> |
> +-- dep A (scope: test)
> |
> |
> +-- dep B (scope: compile)
> |
> |
> +-- dep A (scope: compile)
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
