Could try moving the gwt dependency out of the root pom, keeping it only for 
the client, just gwt-servlet for sever and shared ( unless anyone knows 
better). That will clean up the server dependencies but may cause other 
problems 

Sent from Yahoo Mail on Android 
 
  On Fri, Feb 23, 2024 at 6:44, Ralph Fiergolla<[email protected]> 
wrote:   Don’t want to build up pressure, but yeah that would come in very 
handy 😎
Craig Mitchell <[email protected]> schrieb am Fr. 23. Feb. 2024 um 00:05:

I know it's outside of its scope, but it would be great if 
https://github.com/tbroyer/gwt-maven-archetypes had an example of "If you want 
to create an executable jar with Jetty, this is how you could do it".  🙂

On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:

I tried starting with the tbroyer archetype & to the server project I added the 
app engine stuff from the Google sample to build the appengine-staging 
dependencies directory.Maybe all that should be in a separate project ?

Sent from Yahoo Mail on Android 
 


  On Wed, Feb 21, 2024 at 17:42, Thomas Broyer<[email protected]> wrote:  



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 
isgithub.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 dependencieswhich 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.
  



-- 
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/b4234f67-24c8-4028-8d27-be044a29c733n%40googlegroups.com.



-- 
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/CACwwWxM1fw8YGK7g4rYBxthQUz0%3DS5vPcZtRwTrHCFOOzYLpBg%40mail.gmail.com.
  

-- 
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/25098288.9925314.1708709322047%40mail.yahoo.com.

Reply via email to