[ http://jira.codehaus.org/browse/MWAR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154264#action_154264 ]
paul4christ79 edited comment on MWAR-33 at 11/17/08 1:07 PM: ------------------------------------------------------------- My project team gets hit by this at least twice a week. But shouldn't MWAR-60 have fixed this? It's caused by developer workspaces containing a different version in src/main/webapp/WEB-INF/lib but Maven pulling down a different version in the build process. If we could just exclude WEB-INF/classes and WEB-INF/lib, this problem would be history. was (Author: paul4christ79): My project team gets hit by this at least twice a week. Please let's fix this. > 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