[
http://jira.codehaus.org/browse/MASSEMBLY-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-447.
--------------------------------
Resolution: Won't Fix
Assignee: John Casey
The nearest definition of a dependency's scope always wins in Maven. This is
not an issue with the assembly plugin.
> Redefined scope is ignored for dependencies
> -------------------------------------------
>
> Key: MASSEMBLY-447
> URL: http://jira.codehaus.org/browse/MASSEMBLY-447
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-4
> Reporter: Eric Lewis
> Assignee: John Casey
>
> I have a dependency which is defined with <scope>test</scope>.
> In another project, however, it is redefined to <scope>runtime</scope>.
> Now, when I get the runtime dependencies with
> <dependencySet>
> <useStrictFiltering>true</useStrictFiltering>
> <useProjectArtifact>false</useProjectArtifact>
> <scope>runtime</scope>
> <!-- Don't distribute sources -->
> <excludes>
> <exclude>*:sources</exclude>
> </excludes>
> </dependencySet>
> the dependency is not included.
--
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
