On Thursday, July 21, 2022 at 5:10:40 PM UTC+2 mmo wrote:
> OK - thanks for letting me know! I interpret that such that gwt:run and > gwt:debug aren't working/supported anymore, right? Well, first, regarding the plugin you're using: “The legacy maven plugin is still supported but it is strongly encouraged to use the new one for new projects.” https://gwt-maven-plugin.github.io/gwt-maven-plugin/ That however doesn't mean gwt:run and gwt:debug aren't supported: as long as you don't need jetty-web.xml, they work perfectly fine. Should you use them though? I don't think so (and for many reasons). Do you test and develop in a Tomcat or what's your preferred setup? > My preferred setup is https://github.com/tbroyer/gwt-maven-archetypes/ , with a clear separation of client and server code. This only works with "that other gwt-maven-plugin" that was specifically designed for multi-module Maven projects (well, technically you can make it work with the "legacy plugin", and early versions of the archetypes did just that, but it's too hackish for me). (my actual preferred setup is to not build a WAR, and use Gradle rather than Maven, but that's outside the scope of that discussion) -- 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 on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d5ad99e1-2b05-4f14-a6fc-80a0c8c8356dn%40googlegroups.com.
