I will fix the project documentation and archetype and so on to not include gwt in the goals.
As for GWT taking so long, it really shouldn't? GWT does recompile everything, and that sucks, and we have an issue in the tracker to try to deal with that somehow (though really it's GWT itself that needs to get smarter). But, you shouldn't be seeing all your GWT stuff compile every time you run the shell (the shell just needs the Java source and compiled Java classes, not GWT compiled JavaScript). We have the mojos bound and so on so that gwt:gwt should NOT compile GWT at all - the shell should run using the source and not invoke the GWTCompile mojo. If it's compiling every time you do gwt:gwt, then something is wrong. If you are seeing the GWT compiler involved when you do gwt:gwt, then let me know, the plugin should not be doing that. On Oct 27, 11:01 pm, jieryn <[EMAIL PROTECTED]> wrote: > Removing the <goal>gwt</goal> from my pom.xml solved it. Thank > you. :-) I would recommend that if there are any maven- > googlewebtoolkit2-plugin authors around, that they > updatehttp://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug... > to not have <goal>gwt</goal> listed in common setup pages.. > > Now if only mvn gwt:gwt wouldn't take so long (read: why does GWT > insist on recompiling *everything*? Ugh.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
