POLL: Managing GWT dependencies between 'shared', 'client' and 'server' modules in a multi-module project

[Thomas Broyer]

Dear GWT and Maven users, please chime in re. management of GWT/RequestFactory dependencies in a shared module and transitivity in clientand server modules.

Summary:
Given 3 modules shared, client and server, the former being a dependency of the latter two, and having dependencies on GWT for GWT-RPC or RequestFactory (com.google.gwt.user.client.rpc.RemoteService, orcom.google.web.bindery.requestfactory.shared.EntityProxy et al.), the question is what dependency should shared use (gwt-user vs. gwt-servlet, or gwt-user vs. requestfactory-client vs. requestfactory-server), and how to manage its transitivity inheritance in the client and server modules? (which need either gwt-user, or one of gwt-servlet or requestfactory-server)

Proposals are:

• use scope=provided and have shared and server provide their own dependency (and document the fact that such dependency is required by any project making use of shared)
  
• use either dependency and add an exclusion in one of client or server to replace it with the other. E.g. have shared depend on gwt-servlet and client would exclude it from its dependency on shared and add a dependency on gwt-user; server would transitively depend on gwt-servlet, which is good.
  

Please comment on the Pull Request if you have a GitHub account; otherwise, feel free to comment here:

https://github.com/tbroyer/gwt-maven-archetypes/pull/4#issuecomment-5475092