Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
datanucleus-appengine-1.0.3.jar twice in classpath with Vaadin & GAE Ecplise Plugins #182
Reported by Sami Ekblad on 4 Nov 2009 21:56 UTC
At least then using any JDO classes an exception like this is generated:
java.lang.RuntimeException: Unexpected exception
This makes it impossible to create any Google App Engine / JDO project using the Vaadin Plugin without first manually re-configuring the project classpath.
See also discussion here: http://vaadin.com/forum/-/message_boards/message/76408
Workaround is to remove automatic addition of WEB-INF/lib ("Web App Libraries" class path entry) and add Vaadin jar files from there separately to classpath.
One fix would be that if GAE deployment is selected when creating the project, the plugin should leave out the "Web App Libraries" classpath entry (and add Vaadin jar as separate entry). This is what effectively must be currently done as manual workaround.
Comment by Henri Sara on 6 Nov 2009 09:22 UTC
The problem is in how GAE plugin interacts with the standard Eclipse Web Tools Platform (WTP). The Google plugin is designed to work primarily with its own non-WTP projects, and apparently does not handle WTP projects correctly. There is minimal documentation for using the Google plugin in existing projects (such as WTP), but it does not address this issue.
In summary, considering this a Google plugin WTP incompatibility, not a Vaadin plugin specific problem.