This is really strange. Can you run Maven with -X and check the classpath and arguments passed to GWT? (you may want to also pass -Dgwt.logLevel=INFO)
On Sat, Jul 30, 2016 at 12:56 PM, Thomas Broyer <t.br...@gmail.com> wrote:This is really strange. Can you run Maven with -X and check the classpath and arguments passed to GWT? (you may want to also pass -Dgwt.logLevel=INFO)
Hi,I have run with your parameters, but can't see any mentions nor about gwt-dev.jar nor com.google.gwt.dev.Compiler. Could you point more directly how to check what arguments are passed to GWT?
Ok, same output places with 1.0-SNAPSHOT. Can't see anything nor about src/main/java nor about src/main/resources:
This is by design (sorry, I hadn't worked on the project for months and forgot a bit how it worked in details).src/main/resources (and other resources) is copied (and possibly "filtered") by the maven-resources-plugin, and src/main/java (and other source roots) is copied by gwt:import-sources, so all sources are in (in your case) target/Metrika/WEB-INF/classes.So I'd suggest you check in target/Metrika/WEB-INF/classes that everything's there.Honestly, I don't really understand how things could work with GWT 2.7.0 but fail with GWT 2.8.0-rc1, without changing the gwt-maven-plugin, but work if you move things from src/main/java to src/main/resources.
All I can do is give hints at how to debug the situation.(btw, this is all assuming you "mvn clean" between each change; because… well, Maven)
This is by design (sorry, I hadn't worked on the project for months and forgot a bit how it worked in details).src/main/resources (and other resources) is copied (and possibly "filtered") by the maven-resources-plugin, and src/main/java (and other source roots) is copied by gwt:import-sources, so all sources are in (in your case) target/Metrika/WEB-INF/classes.So I'd suggest you check in target/Metrika/WEB-INF/classes that everything's there.Honestly, I don't really understand how things could work with GWT 2.7.0 but fail with GWT 2.8.0-rc1, without changing the gwt-maven-plugin, but work if you move things from src/main/java to src/main/resources.All I can do is give hints at how to debug the situation.(btw, this is all assuming you "mvn clean" between each change; because… well, Maven)mvn clean - sureRegarding vesions. I didn't try GWT 2.7.0. I was experimenting with 2.8.0-SNAPSHOT, because of this I switched to net.ltgt.gwt.maven plugin. Now I'm confused, but feel positive that 2 weeks ago project was building (with 2.8.0-SNAPSHOT). Now tried 2.8.0-rc1 - problem, also tried GWT 2.7.0 - the same problem as 2.8.0-rc1, so this is not regression, but it is very strange that with 2.8 snapshot I could build project.
It seems that maven-resources-plugin sees couple of files in src/main/resources directory and copies them to target/Metrika/WEB-INF/classes. But thats all. It doesn't copies anything from src/main/java.
And target/Metrika/WEB-INF/classes contains lot of *.class files coming from maven-compiler-plugin, but no *.java files.
I don't see maven-resources-plugin mentioned in my pom files, so it runs with configuration obtained from other plugins. And it seems that it cares to copy src/main/resources only.
Unless you explicitly declare src/main/java as a resource dir, that's the expected behavior.
That means you should copy them yourself; easiest is to use gwt:import-sources (see samples in the GWT SDK, or in the GWT repository)That said, I highly recommend splitting client and server code into separate Maven modules, then you can simply use <packaging>gwt-app</packaging> for the client code and only have to configure the module name and short name.See https://tbroyer.github.io/gwt-maven-plugin/ (intro, usage and migration should help understand the design)