[jira] Updated: (MASSEMBLY-132) Assembly for multi-project ignoring specified scope

["John Casey (JIRA)" <ji...@codehaus.org>]

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

John Casey updated MASSEMBLY-132:
---------------------------------

    Fix Version/s:     (was: 2.2)
                   2.2-beta-1

> Assembly for multi-project ignoring specified scope
> ---------------------------------------------------
>
>                 Key: MASSEMBLY-132
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-132
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: All
>            Reporter: Vinod Panicker
>         Assigned To: John Casey
>            Priority: Critical
>             Fix For: 2.2-beta-1
>
>
> After converting my project to a multi-project, the assembly plugin fails to filter out dependency jars that have a scope other than runtime, even when the scope in the descriptor is explicitly provided.  My dep.xml - 
>   <dependencySets>
>     <dependencySet>
>       <outputDirectory>mims-${version}/lib</outputDirectory>
>       <unpack>false</unpack>
>       <scope>runtime</scope>
>     </dependencySet>
>   </dependencySets>
> I even tried putting exclude statements in the <moduleSet/> <binaries/> section, but even that doesn't work. As a result, the assembly is littered with unnecessary jars such as junit.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira