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
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
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
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
I've got a real simple scaled down GWT application (to illustrate the
issue) with Jetty Embedded Server (9.4.7.v20170914), it can be downloaded
here:
This works fine when running under 2.7.0.
Unfortunately, when I upgrade to 2.8.2, I'm getting an error during the GWT
compilation stage. See
