[
http://jira.codehaus.org/browse/MWAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll closed MWAR-166.
--------------------------------
Assignee: Stephane Nicoll
Resolution: Won't Fix
It's not something that you need to manage in plugins. Use excludes section if
you want to exclude a dependency.
Note that optional works as expected in the latest release
> exclude the transitive dependency
> ---------------------------------
>
> Key: MWAR-166
> URL: http://jira.codehaus.org/browse/MWAR-166
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Michael Meng
> Assignee: Stephane Nicoll
> Priority: Critical
>
> Would you please add a flag which will allow user to have a flexibility to
> include/exclude the transitive dependent jars in the WEB-INF/lib folder?
> The <optional>true</optional> defined inthe dependency is working as desired.
> if we have a war project which depends on A.jar and A.jar transitively
> depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and
> B.jar are both included in the lib folder.
> If we define A.jar as <optional>true</optional>, then A.jar is exclude from
> lib folder, but B.jar are included.
> What we really want is A.jar to be in lib and B.jar not to be include.
> Thanks
--
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
