Re: GWT compile fails with default Maven directory structure

On Friday, November 21, 2014 8:03:42 PM UTC+1, Thomas Broyer wrote:

I can't tell for App Engine, but why would you want a GWT SDK?

You're right, I was able to remove the GWT SDK plugin from Eclipse, and it still works using the one from my maven repository.

That's not the case for GAE. If I remove it, I get the same error that I fixed yesterday by changing the build order to move my Maven Dependencies below everything else, as I mentioned earlier:

GAE SDK /Users/.../.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.15/appengine-api-1.0-sdk-1.9.15.jar failed validation

SDK location '/Users/.../.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.15/appengine-api-1.0-sdk-1.9.15.jar' is not a directory

To get it working again, I need to:

- Reinstall the GAE SDK from GPE

- Change the project to use this SDK temporarily in Project Properties > Google > App Engine. The change won't persist, but it will add the GAE jars to your build classpath.

- Again, move the Maven Dependencies below everything else in Project Properties > Java Build Path > Order and Export

This is a GAE things, but I think more GWT users might run into this. So I can ask the GAE guys about it, but it looks like it's been an issue since at least 2011, so maybe there's a reason why things are the way they are.

Thanks!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.