If you're asking my advice, add a switch/case to your entrypoint based on window.location.pathname, and keep a single entrypoint - will pay off for caching, for compile time, for encouraging code reuse, will produce a single war in a simple `mvn verify` command.
If you want to use the @execution syntax that's fine, but it is definitely not going to be familiar to other developers, and makes it more complex to do things like run tests, etc. The conventions exist because Maven tries to view all kinds of project through the same lens. It does tend to make inventing your own project structure tricky - the other thread you linked has advice on using Gradle or the like if you do want to build your own graph of tasks to perform.
Producing a single war from multiple maven modules is straightforward - make a "webapp" project with packaging=war, and depend on each of the other wars. See https://maven.apache.org/plugins/maven-war-plugin/overlays.html for a discussion of this.
On Saturday, December 28, 2024 at 12:01:35 PM UTC-6 ne...@propfinancing.com wrote:
I was able to get it working by setting the goals in my run configuration to:
clean compile gwt:compile@DiagonalSlitherlink gwt:compile@DiagonalSlitherlink2 war:war
Thank you,
Neil
--
Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com
We offer 30 year loans on single family houses!
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/35550c77-b2db-4631-b75a-b2f68fa02d44n%40googlegroups.com.
No comments:
Post a Comment