[ 
https://jira.codehaus.org/browse/MASSEMBLY-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MASSEMBLY-619:
--------------------------------------

    Component/s: dependencySet
    
> Configurations of different <dependencySet>s influence each other
> -----------------------------------------------------------------
>
>                 Key: MASSEMBLY-619
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-619
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>          Components: dependencySet
>    Affects Versions: 2.2.2, 2.3
>         Environment: Mqven 3.0.4, JDK 1.7
>            Reporter: Olaf Otto
>            Priority: Minor
>
> When configuring two <dependencySet> elements, the configurations in the 
> second influence the first one. 
> h2. Reproduction:
> The following configuration utilizes to sets to copy different elements of 
> the dependency hierarchy of a module into two distinct subfolders:
> {code:xml}
> <dependencySet>
>       <outputDirectory>software</outputDirectory>
>       <useProjectArtifact>false</useProjectArtifact>
>       <excludes>
>               <exclude>org.codehaus.groovy:*</exclude>
>       </excludes>
>       <useTransitiveDependencies>false</useTransitiveDependencies>
> </dependencySet>
> <dependencySet>
>       <outputDirectory>libs</outputDirectory>
>       <useProjectArtifact>false</useProjectArtifact>
>       <includes>
>               <include>org.codehaus.groovy:groovy-all</include>
>       </includes>
> </dependencySet>
> {code}
> However, the first <dependencySet> unexpectedly contains most of the 
> transitive dependencies. The issue can only be resolved by adding 
> <useTransitiveDependencies>false</useTransitiveDependencies> to the second 
> <dependencySet>, too. The issue remains reproducible when changing <scope> 
> <outputMapping> etc. I suppose the isolation of the set configuration is 
> broken. I could reproduce the issue with both 2.3 and 2.2.2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to