Thank you Thomas. This is super helpful. Chris On Tuesday, February 27, 2018 at 7:18:12 AM UTC-5, Thomas Broyer wrote: > > See https://github.com/tbroyer/gwt-maven-archetypes > You'll have to update things a bit of course as these generate WARs that > you run in development with the jetty-maven-plugin; for instance, using an > embedded server would require a dependency:unpack{,-dependencies} and/or > using the maven-assembly-plugin instead of using a war overlay. > > On Monday, February 26, 2018 at 8:53:57 PM UTC+1, Chris wrote: >> >> Thanks Thomas, can you point me to any examples of GWT projects split >> into multiple maven modules? >> I'll head that route. >> >> Thanks again. >> Chris >> >> >> On Monday, February 26, 2018 at 2:03:29 PM UTC-5, Thomas Broyer wrote: >>> >>> apache-jsp brings Eclipse JDT, which causes the conflict. >>> >>> As you're using Mojo's plugin for GWT,you can configure it to put GWT >>> dependencies first in the classpath; that should fix the conflict. >>> >>> But you really should split this project into two or three modules, with >>> separate dependency trees for client and server code. That would >>> automatically clean all such conflicts. >>> >>>
-- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
