Hi - final one today I promise! Another previously discussed issue I'd like to go about implementing is test levels: I have created MAVEN-515 to track it.
proposal: allow multiple unit test sets in the POM justification: some take a long time to run or require resources not always present, and should be omitted in regular development, but run in nightly builds for example. implementation: <unitTest> <type>default</type> (same as if type ommitted) ... as before ... </unitTest> <unitTest> <type>performance</type> ... </unitTest> <unitTest> <type>integration</type> ... </unitTest> <unitTest> <type>touchstone</type> ... </unitTest> By default, just the first is run, but by setting -Dmaven.test.sets=performance,integration Then those will be run (and default which is always run) There will also be the special case of -Dmaven.test.sets=all, which will run everything. Or perhaps test:test-all? They could all use the same unitTestSourceDirectory, or move those into each unitTest set (with code to keep it backwards compatible). Each set would have its own junit report I imagine. Thoughts and objections? Cheers, Brett http://mobile.yahoo.com.au - Yahoo! Mobile - Check & compose your email via SMS on your Telstra or Vodafone mobile. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
