On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1 [email protected] wrote:
I've been trying this app engine sample for Java 11+ which uses a JAR packaged artifact that is installed locally: it provides a Main class to instantiate an HTTP server to run an embedded web application WAR file. github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appengine-simple-jetty-main It has explicit jetty 11 dependencies. The WAR project is github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java11/helloworld-servlet The WAR is run in a local server with: mvn exec:java -Dexec.args="../helloworld-servlet/target/helloworld.war" The problem I have is when I include GWT in the WAR project this draws in Jetty 9 & other dependencies which get copied to the cloud-deployment dependencies directory. This means you WAR have dependencies on gwt-user and/or gwt-dev, that you never want to deploy to a server. The WAR should have a dependency on gwt-servlet only (or requestfactory-server). …and this is exactly what https://github.com/tbroyer/gwt-maven-archetypes were meant to solve. -- 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/c04ab91a-b898-489d-a509-6fafb9a363can%40googlegroups.com.
