[ http://jira.codehaus.org/browse/MWAR-33?page=comments#action_65603 ]
Olivier Lamy commented on MWAR-33: ---------------------------------- Other tests made which causes some troubles. My pom has a dependency to a SNAPSHOT dependecy (in example called foo). An included war dependency has the same dependency. The deployed war dependency contains a timestamped version of this (foo-64456-1.jar). On my machine I have a SNAPSHOT of this (foo-SNAPSHOT.jar) due to an install which include fixes.. When I package my war, the WEB-LIB contains : foo-64456-1.jar foo-SNAPSHOT.jar This cause real trouble and long time debugging to find the trouble because the timestamped one win in the appserver. The ones declares in the pom (and transitive ones) doesn't win. Junit passes but not the application deployed in the appserver. This breaks the maven benefit's because you're really sure about your dependencies. IMO this issue must be set to blocker :-( Olivier > 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 > > > 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
