Re: GWT compile fails with default Maven directory structure

On Friday, November 21, 2014 8:18:19 AM UTC+1, Thomas Broyer wrote:

Sounds like a bug or misconfiguration of the GPE. Is the project a "Maven project" in Eclipse? There might be some hard-coded paths in the GPE (because of limitations of Eclipse) that are only triggered in one or the other "mode" (Maven vs. "simple" Eclipse project). E.g. "/test" being excluded from the GWT Compiler and DevMode classpath in "simple" projects, and the test sources (defaulting to "src/test/java" and "src/test/resources"), as declared in your Maven POM, in Maven projects.

Also, this being a GPE issue, you might have better luck in the dedicated Google Group <https://groups.google.com/d/forum/google-plugin-eclipse> or on StackOverflow.

 

It was created as a Google -> Web Application Project. I think you have it here, it seems that when the source folder base name is 'test', it's excluded from the GWT Compiler, but that's not the case for the default Maven style directory structure.

Just as a general question, do you keep the GPE installed when you use Maven? Where I'm heading is that maybe I only need GPE for the UiBinder auto-completion and editor features. Compiling, DevMode and testing can all be handled with Maven. GPE doesn't seem to keep up with GWT releases anyway.

Thanks for the help...

--
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.