dependency scope for gwt-user should be provided?

32 views
Skip to first unread message

huherto

unread,
Oct 10, 2007, 11:52:02 AM10/10/07
to gwt-maven

Hi, I am new to gwt.

I configured the following dependencies as suggested in the docs:

<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>1.4.60</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-servlet</artifactId>
<version>1.4.60</version>
</dependency>

but if I run "mvn gwt:gwt" I get this error:

[ERROR] Unable to find 'com/google/gwt/user/User.gwt.xml' on your
classpath; could be a typo, or maybe you forgot to include a classpath
entry for source?

If I take out the scope "provided" from the gwt-user dependency it
works ok. But I have a feeling that this may cause problems later on.

Darren Hartford

unread,
Oct 10, 2007, 2:37:01 PM10/10/07
to gwt-...@googlegroups.com
Your problem is not unique. If you use
<scope>compile</scope>, it will work fine -- but will
include the gwt-user.jar in the WAR package which
tomcat doesn't like related to javax.servlet.*
packages.

<scope>provided</scope> solves this, but you may need
to manually add that library to the classpath somehow.
I've had varying success with it.


--- huherto <humb...@itbrain.com.mx> wrote:


____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433

Will Pugh

unread,
Oct 10, 2007, 2:48:58 PM10/10/07
to gwt-...@googlegroups.com
Please create a bug ticket for this, if one is not already around.

I'm thinking the best solution here would be to special case gwt-user,
so if it is marked "provided" it is still put in the ClassPath for
gwt:gwt, but leave other "provided" jars out.

--Will

huherto

unread,
Oct 10, 2007, 4:34:50 PM10/10/07
to gwt-maven
Ok, I will do it.

On Oct 10, 12:48 pm, "Will Pugh" <willp...@gmail.com> wrote:
> Please create a bug ticket for this, if one is not already around.
>
> I'm thinking the best solution here would be to special case gwt-user,
> so if it is marked "provided" it is still put in the ClassPath for
> gwt:gwt, but leave other "provided" jars out.
>
> --Will
>

> On 10/10/07, Darren Hartford <binarymon...@yahoo.com> wrote:
>
>
>
> > Your problem is not unique. If you use
> > <scope>compile</scope>, it will work fine -- but will
> > include the gwt-user.jar in the WAR package which
> > tomcat doesn't like related to javax.servlet.*
> > packages.
>
> > <scope>provided</scope> solves this, but you may need
> > to manually add that library to the classpath somehow.
> > I've had varying success with it.
>

huherto

unread,
Oct 10, 2007, 4:43:26 PM10/10/07
to gwt-maven

MiSt

unread,
Nov 5, 2007, 4:39:39 AM11/5/07
to gwt-maven
On 10 Paź, 21:43, huherto <humbe...@itbrain.com.mx> wrote:
> A bug ticket was created:
>
> http://code.google.com/p/gwt-maven/issues/detail?id=64

I have provided simple patch for this (for 2.0-beta).

Reply all
Reply to author
Forward
0 new messages