modules not detected when in src/main/resources about gwt-eclipse-plugin

[branflake2267]

I've been wondering about this too. Does this happen in GPE too?

[dodgex]

hey i left the office right after opening this issue. if it is ok i'll check on monday on one of our other eclipse installations.

[branflake2267]

I was curious no hurry.

[metteo]

I think this might be related to the way how m2e handles src/main/resources. It adds exclude for that src folder. Something like /*. If you remove it, gwt.xmls should be detected.

EDIT: IIRC this is done on purpose because of maven filtering.

[branflake2267]

I forget, the source paths for resources, or any other paths, m2e sets up to excludes by default. I remember thinking this is annoying because I want them included in the build path.

[branflake2267]

Adding some notes. m2e default configuration is to exclude resources directory from the build path.

[branflake2267]

https://www.eclipse.org/m2e/documentation/m2e-faq.html - resources are excluded by default can be found here. I should configure the maven builder include these.

[branflake2267]

https://github.com/gwt-maven-plugin/m2e-gwt - could integrate this feature, or use it to solve it...

[branflake2267]

I'll aim to add the lifecycle goals to the import process just for this particular maven plugin.

[branflake2267]

https://github.com/tbroyer/gwt-maven-plugin/blob/master/src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml - Broyer's plugin lifecycle...

[branflake2267]

mvn gwt:resources or the resource mojo copies the files into the web-inf/classes directory. This isn't in the classpath so it's a problem still. I did notice that target/generated-sources gets set up as a source folder on a second maven update and if it were copied to this folder could work. m2e-gwt plugin doesn't do much in this case. I'm going to push the priority down on this because there are a couple workarounds in the meantime.

[geoffreywiseman]

Colleague got bit by this recently -- any change?