You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/03/09 23:21:40 UTC

[jira] [Comment Edited] (MSHADE-220) Shade test-scoped dependencies of test jars

    [ https://issues.apache.org/jira/browse/MSHADE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188183#comment-15188183 ] 

Michael Osipov edited comment on MSHADE-220 at 3/9/16 10:21 PM:
----------------------------------------------------------------

There is no bug here. The goal description clearly says:

bq. Requires dependency resolution of artifacts in scope: runtime.

You cannot select the dependency scope.

You are probably best set with the Assembly Plugin and a custom assembly.


was (Author: michael-o):
There is no bug here. The goal description clearly says:

bq. Requires dependency resolution of artifacts in scope: runtime.

You cannot select the dependency scope.

> Shade test-scoped dependencies of test jars
> -------------------------------------------
>
>                 Key: MSHADE-220
>                 URL: https://issues.apache.org/jira/browse/MSHADE-220
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4.3
>            Reporter: Joel Friedly
>
> I have a trivial smoketest project that creates a shaded executable jar so that I can just copy my smoketest jar to any host and run it.  My smoketest project doesn't actually contain the test cases though, it just depends on the test jar produced by our main integration testing submodule.  Shade will shade in the compile-scoped dependencies of this test jar, but not the test-scoped dependencies of this test jar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)