On Oct 4, 2013, at 5:18 PM, Andreas Dolk <andreas.dolk.mo...@googlemail.com> wrote:
> Hi all, > > we have a rather complex project structure with a lot of projects and a > couple of code generators that produce java classes for production and > test. The challenge now is to configure the build files so that a mvn > eclipse:eclipse run will create all required source folders and set the > correct output folders, for example: What happens if you run: mvn test-compile eclipse:eclipse instead of just mvn eclipse:eclipse By default, eclipse:eclipse just runs far enough to get the source directories, not all the test directories. If you force maven to run to the test-compile phase, then it should be able to pick everything up. Dan > > src folder: src/main/code-gen > out folder: (default) -> target/classes > > src folder: src/test/code-gen > out folder: target/test-classes > > Currently we use the maven build helper to set the source folders but I > still don't know how to set the out dirs - now it creates a project config > that compiles production and test classes into the same out folder which > actually causes conflicts. > > Is there any way to "fine-tune" the .classpath file programmatically? > > Cheers, > > Andreas -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
