[
http://jira.codehaus.org/browse/MWAR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111153
]
Stephane Nicoll commented on MWAR-33:
-------------------------------------
Scott, we would like to have this as well but this needs a heavy change in the
maven core. I think it's been scheduled for 2.1 but I'm not sure.
What I would like to implement for this is a WEB-INF/lib postpackagingtask that
will scan WEB-INF/lib and will report any duplicate dependencies that is found.
A strict mode flag (set to false by default) can fail the build if a duplicate
is found.
I hope this will be a first solution till we have the ability to resolve the
war's transitive dependencies.
Brian, does that help? Any suggestion?
> jars with differents versions can be in WEB-INF/lib with war as dependencies
> ----------------------------------------------------------------------------
>
> Key: MWAR-33
> URL: http://jira.codehaus.org/browse/MWAR-33
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Environment: all
> Reporter: Olivier Lamy
> Fix For: 2.1-alpha-2
>
> Original Estimate: 15 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> My pom has the following dependencies :
> - log4j:log4j:1.2.13
> - a war with log4j:log4j:1.2.11 included
> Result the two jars are in WEB-INF/lib.
--
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
