[jira] [Commented] (MASSEMBLY-919) Transitive dependency of a test dependency is included

["Mark Struberg (Jira)" <ji...@apache.org>]

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

Mark Struberg commented on MASSEMBLY-919:
-----------------------------------------

I was not able to reproduce your problem.

I've now created an integration test over here: [https://github.com/struberg/maven-assembly-plugin/tree/MASSEMBLY-919]

Can you please check if this represents your scenario? You can run the single IT with the following command:
{noformat}
mvn verify -Dinvoker.test=it-project-parent,projects/bugs/massembly-919 -Prun-its{noformat}

> Transitive dependency of a test dependency is included
> ------------------------------------------------------
>
>                 Key: MASSEMBLY-919
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-919
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>          Components: dependencySet, filtering
>    Affects Versions: 3.1.1
>            Reporter: Zsombor Gegesy
>            Assignee: Mark Struberg
>            Priority: Blocker
>              Labels: patch-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I have a simple module, with one compile 'module-a' dependency, and with one test dependency ('module-b'), which has a couple of 'compile' dependencies (module-b-1, module-b-2, etc)
> In my assembly.xml I have:
> {code:java}
>     <dependencySets>
>         <dependencySet>
>             <useProjectArtifact>true</useProjectArtifact>
>             <outputDirectory>tools</outputDirectory>
>             <unpack>false</unpack>
>             <!-- runtime scope assembles compile and runtime dependencies, but skips those with provided scope. -->
>             <scope>runtime</scope>
>             <useTransitiveFiltering>true</useTransitiveFiltering>
>         </dependencySet>
>     </dependencySets>
> {code}
> I would assume, that in this case, only 'module-a.jar' ends in the tool folder, however, the plugin adds module-b-1, module-b-2, etc too - which is not expected, as they are  dependencies of 'module-b', which has test scope only.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)