[ http://jira.codehaus.org/browse/MWAR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163567#action_163567 ]
Alex Rau commented on MWAR-33: ------------------------------ Huge show stopper for us. We extend a 3rd party product and the current state of the WAR plugin forces us to redeclare > 100 3rd party dependencies which is practically *impossible*. Brett - IMHO you described a proper solution (ignore/empty out WEB-INF/lib, resolve *all* deps only using project descriptors). Is this really that tricky to implement (sounds like loads of efforts) - especially considering that this issue is years old - what about current versions of maven ? Regarding WEB-INF/lib: there's no point in using a tool like Maven for dependency management and then rely on plain old files (like ant) for web applications - this is definitely not following the "declaration" concept of Maven. > 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 > Assignee: Stephane Nicoll > Fix For: 2.1 > > 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