On Saturday, February 23, 2019 at 12:55:17 PM UTC+1, Ralph Roland wrote:--
Given your description, you could create fewer Maven modules (I'm not saying you should do it, but you could)
* shared, with common.shared, app_a.shared and app_b.shared
* common-client, as a gwt-lib, with common.client, and depending on shared and shared-sources
* app_a, as a gwt-app, with a dependency on common-client and shared (and shared-sources), though that one is also brought transitively through common-client
* app_b, as a gwt-app, with a dependency on common-client and shared (same as app_a)
* server, as a war, with common.server, app_a.server and app_b.server, and a dependency on shared.
Note that you could technically also use a single Maven module mixing client and server code, but this means your server-side dependencies are in your client code classpath (compile and "runtime"), and your client-side dependencies are in your server compile classpath (not runtime if you correctly exclude them from your WAR). If that's how you manage your classpaths with Ant, then it could provide an easier migration path to Maven; see https://github.com/gwtproject/gwt/blob/2.8.2/user/src/com/google/gwt/user/tools/templates/maven/pom.xmlsrc for an example setup (this is the template used by GWT's WebAppCreator)
BTW - my main reason for wanting to move to a maven-based build is to manage the dependent jars in the web-inf/lib directory.
If that's your main driver and you're otherwise OK with Ant, then maybe have a look at Ivy.
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 firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Post a Comment