On 2011/08/12 21:05:01, rchandia wrote:
From an offline note sent by Rodrigo:
This maven project is far from perfect though:
- Gwtc complains that gwt-dev.jar is in the classpath (but this is
necessary to compile the linker)
- The deployed app contains symbol maps (which can't be removed because
gwtc runts too late in the maven phases)
- Contains compiled client class files and the linker classes (but they
are needed for DevMode and gwtc runs too late)
In truth this sample should rather use a multi-project maven structure
(composed of gae, client, server and linker sub-projects), but:
- I did not want to pollute the fixes with a folder reorganization
- It makes the sample harder to use:
- First it would require a 'mvn install' from the root of the sample
to ensure gae dependencies are reachable (the client, server and linker
projects)
- Then, to perform any 'mvn {gwt,gae}:xxx' operation it would be
necessary to cd to the gae sub-project
Would it be worthwhile to make this change in structure?
http://gwt-code-reviews.appspot.com/1521803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
