SuperDevMode and validation-api

[Ümit Seren]

I am trying to switch to SuperDevMode in one project and I run into an issue with missing source code. 

It's a normal maven2 project configured with m2e in eclipse. It compiles fine when I compile it manually however when I start the codeserver for SuperDevMode I get following error (not using maven but creating a run configuration in eclipse):

[ERROR] Line 113: No source code is available for type javax.validation.ConstraintViolation<T>; did you forget to inherit a required module?

I have the validation-api 1.0.0.GA sources as a maven2 dependency. 

The run configuration for the codeserver looks like following: 

-src src/main/java/ 

-src target/generated-sources/annotations/

MyModule

The classpath contains the maven2 dependencies and the project. 

Am I missing something here?

thanks in advance

P.S: I had a similar issue with a custom maven dependency. SuperDevMode couldn't find the libraries Module xml (I had the library linked using eclipse m2e's workspace resolutions). It only started to work after I installed the SNAPSHOT version of the library into the local maven repository. Not sure if these issues are related

[Ümit Seren]

I was only able to fix this by manually adding the
validation-api-1.0.0.GA-sources.jar to the user entries of the
classpath of my run configuration for superdevmode.

> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/hNYplu7E0RUJ.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.

[Thomas Broyer]

On Tuesday, October 9, 2012 11:39:35 AM UTC+2, Ümit Seren wrote:

I was only able to fix this by manually adding the
validation-api-1.0.0.GA-sources.jar to the user entries of the
classpath of my run configuration for superdevmode.

This is maybe because sources jars have the addedToClasspath bit to false, which Eclipse respects, but not the gwt-maven-plugin (it takes all dependencies in the maven scope independently of their type or classifier).

http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven/maven-core/3.0.4/META-INF/plexus/artifact-handlers.xml

[Ümit Seren]

Thanks Thomas for the info, that makes sense

The reason I am not using mvn gwt:run-codeserver is that I have some
custom libraries which I add as dependency to my main project using
eclipse m2e's workspace resolution and I haven't been able to run mvn
commands from eclipse respecting the workspace resolution ( I get
missing dependency errors).

Of course I could install the SNAPSHOTS of my custom libraries into
the local maven repository but most of the time I am too lazy.

> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-web-toolkit/-/dgD0slxX4Y0J.

[Thomas Broyer]

On Tuesday, October 9, 2012 1:21:06 PM UTC+2, Ümit Seren wrote:

Thanks Thomas for the info, that makes sense

The reason I am not using mvn gwt:run-codeserver is that I have some
custom libraries which I add as dependency to my main project using
eclipse m2e's workspace resolution and I haven't been able to run mvn
commands from eclipse respecting the workspace resolution ( I get
missing dependency errors).

Yes, this is a known issue (true for all gwt-maven-plugin goals): https://jira.codehaus.org/browse/MGWT-332

And FWIW, I also run DevMode and SuperDevMode from within Eclipse (for the exact same reason, and also because it makes debugging with DevMode so much easier!)