|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
[mojo-dev] [jira] (MGWT-325) Jars included twice in classpath lead to ClassCastExceptions
Constantino Cronemberger (JIRA) Tue, 27 Nov 2012 09:06:16 -0800
- [mojo-dev] [jira] (MGWT-325) Jars included... Constantino Cronemberger (JIRA)
- [mojo-dev] [jira] (MGWT-325) Jars inc... Constantino Cronemberger (JIRA)
- [mojo-dev] [jira] (MGWT-325) Jars inc... Marko Krajnc (JIRA)
- [mojo-dev] [jira] (MGWT-325) Jars inc... Marko Krajnc (JIRA)
- [mojo-dev] [jira] (MGWT-325) Jars inc... Constantino Cronemberger (JIRA)

The solution I have implemented was: Only log4j jar and jars with "*.gwt.xml" files are added to the classpath. These jars will be both in the classpath and in WEB-INF/lib and the others only on WEB-INF/lib. The check to see if a jar has a *.gwt.xml is quite fast, so I think it is OK.