Found in GWT Release (e.g. 1.5.3, 1.6 RC):

2.1 RC1

Detailed description (please be as specific as possible):

Rajeev Dayal reported:

I see the following in the pom.xml file:

<dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt-user</artifactId> <version>2.1-SNAPSHOT</version> <scope>provided</scope> </dependency>

Really, shouldn't the scope be "compile"?

Ray Cromwell added a comment - 09/Oct/10 12:19 AM provided is the same as compile, except that compile scope gets packaged into the war and it's not transitive. We don't want gwt-user.jar ending up in the WEB-INF/lib directory. If this is causing trouble, we could change it to compile, but then add rules to the war-plugin to specifically exclude gwt-user.

Thomas Broyer added a comment - 09/Oct/10 12:43 AM According to the Maven FAQ, it should really be "provided": http://maven.apache.org/general.html#scope-provided

Links to relevant GWT Developer Forum posts:

https://jira.springsource.org/browse/ROO-1484

The problem with provided scope is that provided jars aren't downloaded from the maven repo automatically. If everything in gwt-user is also in gwt-servlet (see 5376), this will be OK, but it's not ideal.

gwt-user should be in the default (compile) scope so it can be downloaded automatically from a Maven repo. It can be excluded from WEB-INF/lib by configuring the war plugin as Ray suggests.

!?

I'm not a Maven guy (started using it at the time GWT 2.1 M1 was released) and never had that issue: gwt-user configured as scope=provided and everything always compiled OK (from both M2Eclipse and our Hudson CI server)

My mistake, closing this issue.