[
http://jira.codehaus.org/browse/MASSEMBLY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121796
]
Sejal Patel commented on MASSEMBLY-268:
---------------------------------------
Yes it does very much sound like a bug to me. The other plugins and bundlings
all "exclude" any depedency marked as "provided". Because it is suppose to be
provided by whomever uses it. Thus it shouldn't be bundled up to began with.
> Descriptor bundling dependency sets should contain tag <useScopeOnly>
> ---------------------------------------------------------------------
>
> Key: MASSEMBLY-268
> URL: http://jira.codehaus.org/browse/MASSEMBLY-268
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-1
> Reporter: Michael Osipov
>
> I am bundling bin distros and include in folders my dependency sets:
> say I have this:
> <pre>
> <dependencySets>
> <dependencySet>
> <outputDirectory>lib</outputDirectory>
> <scope>complile</scope>
> </dependencySet>
> </dependencySets>
> </pre>
> It bundles al libs which are necessary to compile, means compile, provided
> which makes sense. Hence, I want to be able to include libs exclusively from
> a scope.
> Like
> <pre>
> <dependencySets>
> <dependencySet>
> <outputDirectory>lib</outputDirectory>
> <scope>complie</scope>
> <useScopeOnly>true</useScopeOnly>
> </dependencySet>
> </dependencySets>
> </pre>
> which basically mean it will include only those libs which have been declared
> compile and no provided. Tag should default to false.
--
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
