Inclue Google private changes into mojo plugin
----------------------------------------------
Key: MGWT-229
URL: http://jira.codehaus.org/browse/MGWT-229
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Reporter: nicolas de loof
Attachments: gwt-maven-plugin-1.3.2.google-sources.zip
Here are the changes made by Google guys internally into the "2.1.google"
version of the plugin to support GWT / GAE / Maven and Eclispe together
Hacked version of the gwt-maven-plugin 1.3-SNAPSHOT that fixes
the following problems:
1) Google AppEngine SDK will not run from jars in separate
directories, it expects a very specific disk layout, so this patch
detects when DevMode is invoked with DevAppServer and adds jars from
an unpacked SDK dependency.
2) AppEngine SDK fails in DevMode if certain jars appear on
the system classpath, namely asm-3.3.jar. This patch filters out. In
reality, DevMode should provide ways to separately define the GWT and
WebApp classpaths and not require dumping everything on the system
classpath.
3) A new <copyWebApp> directive is added, which copies the War
source directory into the web app directory. This makes
DevMode/AppEngine happier and allows "gwt:run" to run without a
gwt-compile step.
A less hack version would
a) not hardcode asm-3.3.jar filtering, but allow either plugin
configation to exclude jars from the system classpath, or
automatically filter out jars that were picked up by plugin
dependencies (e.g. datanucleus enhancer adds asm-3.3.jar to
dependencies)
b) allow configuration of the AppEngine SDK inclusion in step
#1. Currently hardcoded to AppEngine 1.3.7 jars
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
