[ http://jira.codehaus.org/browse/MWAR-33?page=comments#action_67810 ]
Brett Porter commented on MWAR-33: ---------------------------------- ok, it took me a bit to realise this was because the war is being unpacked. You should use warExclude for now. This is a much bigger change that will require excluding WEB-INF/lib *and* pulling in the dependencies from the dependant WAR using the maven artifact mechanism. I don't think it's a good idea to exclude the WEB-INF/lib by default without that, though. > 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 > Type: Bug > Environment: all > Reporter: Olivier Lamy > Fix For: 2.1 > > Original Estimate: 15 minutes > Time Spent: 30 minutes > Remaining: 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
