I believe that's how it works now. The root pom just has the dependencyManagement ( https://github.com/tbroyer/gwt-maven-archetypes/blob/main/modular-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml#L17 ). It doesn't actaully include it as a dependency.
The server and shared module poms include the gwt-servlet lib, and the client pom includes the gwt-user + gwt-dev libs.
On Saturday 24 February 2024 at 4:29:28 am UTC+11 Tim Macpherson wrote:
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
On Fri, Feb 23, 2024 at 6:44, Ralph Fiergolla<ralph.f...@gmail.com> wrote:Don't want to build up pressure, but yeah that would come in very handy 😎--Craig Mitchell <ma...@craig-mitchell.com> 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 ?On Wed, Feb 21, 2024 at 17:42, Thomas Broyer<t.br...@gmail.com> wrote:On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1 tim_mac...@yahoo.co.uk 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.It has explicit jetty 11 dependencies.The WAR project isThe 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 google-web-tool...@googlegroups.com.
To view this discussion on the web visit
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-tool...@googlegroups.com.
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 google-web-tool...@googlegroups.com.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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/749569e3-371c-4287-8dff-157c65bc6934n%40googlegroups.com.
No comments:
Post a Comment