Hello,
I found it!
The error is caused by the following dependency:
<dependency>
<groupId>msm.lib.acs</groupId>
<artifactId>msm-lib-acs</artifactId>
<version>1.0-SNAPSHOT</version>
<!--
<scope>provided</scope>
-->
</dependency>
The error immediately disappears when I set the scope to provided again.
Now I can enable dependency resolution in eclipse again.
So far so good. But I also remember why I removed the provided scope.
Juan recommended this in another thread
<https://groups.google.com/d/msg/google-web-toolkit/pZvsDZwkrWY/FNaIG8yLAgAJ>
as a solution to another problem:
My app uses my lib (msm.lib.acs above), and my lib uses common libs from
the maven repository, e. g. postgresql-42.0.0.jar.
The problem was that those libs were not copied into the application's
WEB-INF/lib folder. So I ended up in missing jars.
And unfortunately this problem now reappeared. When I build the app with
"mvn package", I end ab with a WEB-INF/lib folder not containing the
external libs!
So I made one step backward, dependency resolution is enabled again, but
the external jars are missing in the app folder.
Maybe another scope is better?
Magnus
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
