Yeah, the current build setup is a little tricky and doesn't follow the maven conventions.
The reasons is that the IDE GWT plugins expect a specific directory structure.
But to answer your question. It's part of the build configuration:
<build> <!-- include module descriptors from src/main/java in order not to break the Intellij GWT plugin --> <resources> <resource> <directory>src/main/java</directory> </resource> </resources> </build>
If you use the maven archetype we ship, everything should be layed out correctly.
Heiko, yeah that makes sense. Maybe you should add it as a caveat in your user guide, for folks trying out their own workspaces.
If you use the archetype, I guess you do not have this issue, but that cannot be always the case where people may have their own build infrastructure, in which case, a tip/warning will be greatly beneficial.
In a different project, I am facing problems with explicitly specifying directories (source, output, resources) etc in the build config because the maven source jar plugin bundles the source code in a wrong way. More like a domino effect with maven.
I just moved the Errai* properties to src/main/resources and that takes care of things. I do not need to specify the resource directories in the build configuration.