I think it all has to do with the new lifecycle introduced by the new Maven plugin.
I am personally not using the new packaging, keeping the runnable module with "war" packaging, all other modules with "jar" packaging and forcing execution of the GWT compilation goal for use as overlay in a downstream module with a "war" packaging. This satisfies the requirements of my projects which rely on use of overlays in downstream modules with a "war" packaging. Other projects could be having different requirements for which the Maven plugins new lifecycle could be suitable. On Friday, 4 April 2025 at 04:33:04 UTC+1 Craig Mitchell wrote: Maybe my situation was different. Google App Engine required an executable war / jar. Ie: It must run like this "java -jar my-app.war". The GWT Eclipse Plugin couldn't build this, thus I switched to the GWT Maven plugin. But I admit, the GWT Maven plugin is a little confusing. Right now, my top level pom has "<packaging>pom</packaging>". My client module has "<packaging>gwt-app</packaging>". And my server module has "<packaging>war</packaging>". Why is the client packaging called "gwt-app", why not just called it "war" like the server. And why does it need to know how the server will be packaged at all, isn't the client just converting Java to JS? Anyway, it works, and that's the main thing. 🙂 On Friday, 4 April 2025 at 1:40:08 pm UTC+11 [email protected] wrote: The GWT Eclipse Plugin primarily understands Maven modules with "war" packaging, Maven WAR Plugin and GWT in the classpath. It also somehow understands some of the GWT Maven Plugin directives creating DevMode and codeserver run configurations accordingly. I have been using this for longer than I can remember and it is still working out of the box without any complications, quick and easy. Hence my original thought about convergence, so that the plugins can keep working together. On Friday, 4 April 2025 at 03:06:12 UTC+1 Craig Mitchell wrote: My experience. I was initally using the GWT Eclipse Plugin, along with the GAE (Google App Engine) Eclipse Plugin. Everything worked out of the box, and was simple. However, GAE then dropped support for the GAE Eclipse plugin, and required me to use Maven (or something similar) and supply my own server. This wasn't supported by the GWT Eclipse Plugin, so I switched to use the GWT Maven plugin. It was more complicated, but more flexible. At no point did I think the GWT Eclipse Plugin would work alongside the GWT Maven Plugin. They build things differently. On Friday, 4 April 2025 at 8:00:11 am UTC+11 Thomas Broyer wrote: On Thursday, April 3, 2025 at 8:19:21 PM UTC+2 [email protected] wrote: I am actually creating Eclipse run configurations of "GWT Development Mode (DevMode)" type, with built-in server port and "Super Development Mode" option which is quite similar to your approach but without separate steps for "codeserver" and application startup. This is required to keep the running steps as uniform and simple as possible for the members of my teams, a single and easy to create Eclipse run configuration for each GWT app. The GWT Eclipse Plugin apparently has some way to launch both GWT CodeServer and a server with Eclipse WTP at the same time (autoconfiguring the CodeServer launchDir and startupUrls): https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html Or you could maybe use a "Launch Group" launch configuration to run both the server and client in one click ? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/226eed49-3712-4d32-8668-14ca6ec71481n%40googlegroups.com.
