The following comment has been added to this issue:
Author: thierry lach
Created: Tue, 8 Jun 2004 12:39 PM
Body:
If a source directory and destination directory tag were added (as in the following
example) then <unitTestSourceDirectory/> and <integrationUnitTestSourceDirectory/>,
and the variety of test plugin properties (e.g. maven.test.dest, maven.iutest.dest)
could be deprecated and removed.
<unitTest>
<sourceDir>${basedir}/src/test-default/java</sourceDir>
<destDir>${maven.build.dir}/test-default/classes</destDir>
<type>default</type> (same as if type ommitted)
... as before ...
</unitTest>
<unitTest>
<sourceDir>${basedir}/src/test-performance/java</sourceDir>
<destDir>${maven.build.dir}/test-performance/classes</destDir>
<type>performance</type>
...
</unitTest>
<unitTest>
<sourceDir>${basedir}/src/test-cactus/java</sourceDir>
<destDir>${maven.build.dir}/test-cactus/classes</destDir>
<type>cactus</type>
...
</unitTest>
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-515?page=comments#action_20473
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-515
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-515
Summary: unit test levels
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
model
Fix Fors:
1.1
Assignee: Brett Porter
Reporter: Brett Porter
Created: Mon, 23 Jun 2003 9:53 AM
Updated: Tue, 8 Jun 2004 12:39 PM
Description:
This is to track the progress of what is decided about this feature. Once again, happy
to implement when I get time as I need it for work :)
here is the proposal sent to the list:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
