maven-plugins/test/xdocs/changes.xml
jstrachan f2643277b2 A patch so that the test plugin can use the test classes directory - rather than just the test source code directory - for searching for unit test cases to run.
The default behaviour remains unchanged - however this new feature allows other languages which compile down to bytecode - like Groovy - to be used and found by the default unit test run.

This mechanism could also be useful if other test classes are copied or code generated into the target/test-classes directory etc.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114042 13f79535-47bb-0310-9956-ffa450edef68
2003-09-19 16:26:50 +00:00

49 lines
1.7 KiB
XML

<?xml version="1.0"?>
<document>
<properties>
<title>Changes</title>
<author email="dion@multitask.com.au">dIon Gillard</author>
</properties>
<body>
<release version="1.5" date="in CVS">
<action dev="jstrachan" type="fix">
You can now specify whether the source (java) or classes (class) files
are searched when using the test plugin via the property:
maven.test.search.classdir. It defaults to use (java) to preserve
backwards compatibilty. Using (class) allows you to work with alternative
languages that compile to bytecode like
<a href="http://groovy.codehaus.org/>Groovy</a>
</action>
</release>
<release version="1.4" date="in CVS">
<action dev="evenisse" type="fix">
Check if unitTest tag is present in pom before copy resources.
</action>
</release>
<release version="1.3" date="Unknown">
<action dev="evenisse" type="add">
Add jvmarg support for junit.
Add properties documentation.
</action>
</release>
<release version="1.2" date="2003-02-11">
<action dev="evenisse" type="fix">
Fixed classpath for test:ui, test:single and test:match goals.
</action>
<action dev="dion" type="fix">
Added xmlapis and xerces to project dependencies as per MAVEN-106
bug report
</action>
</release>
<release version="1.1" date="2002-10-01">
<action dev="vmassol" type="fix">
The test plugin now works again if the project has not
tests defined. The introduction of the &lt;test:test-resources&gt;
goal had broken this feature.
</action>
</release>
</body>
</document>