[
http://jira.codehaus.org/browse/MDEP-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252782#action_252782
]
Tuomas Kiviaho commented on MDEP-266:
-------------------------------------
I draw hasty conclusions about this issue. Optional dependencies declared in
project are included as per my personal tests but optional dependencies of
project's transitive dependencies are not (unless they are re-declared in the
project), if I'm correct this time around. This would be the standard procedure
and I doubt that it would be trivial to include optional dependencies behind
transitive dependencies since they are not available for the plugin when it
starts the filtering
PS. I noticed that there's currently no way to exclude optional dependencies
(and their transitive dependencies) of the project.
PPS. My problem with classpath seems to be reported already at MDEP-107
> Add parameter to configure copy-dependencies to also copy optional
> dependencies
> -------------------------------------------------------------------------------
>
> Key: MDEP-266
> URL: http://jira.codehaus.org/browse/MDEP-266
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
> Components: copy-dependencies
> Affects Versions: 2.1
> Reporter: Andreas Sewe
> Assignee: Brian Fox
> Priority: Minor
>
> At the moment, copy-dependencies only copies non-optional dependencies.
> However, one sometimes wants to copy *all* dependencies -- even the optional
> ones.
--
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
