It looks like integration testing will need to be done in a profile. IMO, that's really not such a bad thing. In fact, it could be fairly clean.
If there is additional integration testing support to come, then it will have to wait until Maven 2.1. This may mean we bring forward the deadline for 2.1 and make it a smaller feature release focusing on some key objectives - things that are currently impossible or very difficult to use. That is likely a good idea anyway. - Brett Pablo wrote: > Brett Porter wrote: > >>> What would be the best solution? Changing one of the standard >>> compiler mojos? >>> Adding additional generic mojo without "readonly"'s, with possibility >>> to set >>> source roots, etc? Maybe something else. I don't like what we had to >>> do - copy/paste a lot of source from one of maven-compiler-plugin mojos. >>> >>> Pablo from my team wrote about it today, and Bob Allison here: >>> http://jira.codehaus.org/browse/MCOMPILER-13. >>> >> >> I thought this was too much of a coincidence :) >> >> Use the build-helper-maven plugin from org.codehaus.mojo. >> >> >> From > http://mojo.codehaus.org/build-helper-maven-plugin/add-source-mojo.html: > > |sources| /(Optional)/ |File| |-| |-| Additional source > directories > > > I've never used this plugin but what I understand of it is that this > plugin adds additional directory. > *Add a source directory* to POM (from plugin's site). > Therefore a directory set in Mojo as a default one is also included. > In that case target/integration-tests would also include unit test > classes from target/test-classes (compiled sources from src/tests).. > Am I right? If so, it's not a solution. > > Cheers > Pablo > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
