Initial revision
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@112724 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
1 parent
66e44f2734
commit
530c640d4f
821 files changed
+55754
No files matched your search
@@ -0,0 +1 @@
|
||||
stylesheets
|
||||
@@ -0,0 +1,27 @@
|
||||
<?xml version="1.0"?>
|
||||
<document>
|
||||
<properties>
|
||||
<title>Changes</title>
|
||||
<author email="dion@multitask.com.au">dIon Gillard</author>
|
||||
</properties>
|
||||
|
||||
<body>
|
||||
<release version="1.2" date="in CVS">
|
||||
<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 <test:test-resources>
|
||||
goal had broken this feature.
|
||||
</action>
|
||||
</release>
|
||||
</body>
|
||||
</document>
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
|
||||
<document>
|
||||
<properties>
|
||||
<title>Maven test Plug-in Goals</title>
|
||||
<author email="dion@apache.org">dIon Gillard</author>
|
||||
</properties>
|
||||
<body>
|
||||
<goals>
|
||||
<goal>
|
||||
<name>test</name>
|
||||
<description>Test the application</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:compile</name>
|
||||
<description>Compile the TestCases and TestSuites</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:match</name>
|
||||
<description>Execute all the tests matching the given 'testmatch' variable</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:match-test</name>
|
||||
<description>[deprecated] please use the test:match goal instead</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:prepare-filesystem</name>
|
||||
<description>Create the needed directory structure</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:single</name>
|
||||
<description>Execute a single test defined using the 'testcase' variable</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:single-test</name>
|
||||
<description>[deprecated] please use the test:single goal instead</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:test</name>
|
||||
<description>Test the application</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:test-resources</name>
|
||||
<description>Copy any resources that must be present for run tests</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>test:ui</name>
|
||||
<description>Starts the Swing TestRunner front end</description>
|
||||
</goal>
|
||||
</goals>
|
||||
</body>
|
||||
</document>
|
||||
@@ -0,0 +1,16 @@
|
||||
<?xml version="1.0"?>
|
||||
<document>
|
||||
|
||||
<properties>
|
||||
<title>Maven Test Plugin</title>
|
||||
<author email="jason@zenplex.com">Jason van Zyl</author>
|
||||
</properties>
|
||||
|
||||
<body>
|
||||
<section name="Maven Test Plugin">
|
||||
<p>
|
||||
This plug-in provides your basic JUnit testing facilities.
|
||||
</p>
|
||||
</section>
|
||||
</body>
|
||||
</document>
|
||||
@@ -0,0 +1,16 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<project name="Maven Test Plugin">
|
||||
|
||||
<title>Maven Test Plugin</title>
|
||||
|
||||
<body>
|
||||
<links>
|
||||
<item name="Maven" href="http://jakarta.apache.org/turbine/maven/"/>
|
||||
<item name="JUnit" href="http://junit.sourceforge.net/"/>
|
||||
</links>
|
||||
<menu name="Overview">
|
||||
<item name="Goals" href="/goals.html"/>
|
||||
<item name="Properties" href="/properties.html"/>
|
||||
</menu>
|
||||
</body>
|
||||
</project>
|
||||
@@ -0,0 +1,135 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<document>
|
||||
|
||||
<properties>
|
||||
<title>Test Properties</title>
|
||||
<author email="smor@apache.org">Stéphane MOR</author>
|
||||
</properties>
|
||||
|
||||
<body>
|
||||
<section name="Test Settings">
|
||||
<table>
|
||||
<tr><th>Property</th><th>Optional?</th><th>Description</th></tr>
|
||||
<tr>
|
||||
<td>maven.junit.fork</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
When using Java 1.4, it may be necessary to fork the JUnit
|
||||
tests to prevent XML parser issues. The default value is
|
||||
<code>no</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.junit.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
The directory to invoke the VM in. (ignored if fork is disabled).
|
||||
The default value is <code>${basedir}</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.junit.usefile</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
If this value is set to false, JUnit test run details will appear on
|
||||
the console as the tests are executed. If not, they are stored in
|
||||
a file in the <code>test-reports</code> directory. The default value
|
||||
is <code>true</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.test.dest</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the unit test classes directory. This is the
|
||||
location where the java classes for the test source
|
||||
code will be generated to. The default value is
|
||||
<code>${maven.build.dir}/test-classes</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.test.source</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Provide source compatibility with a specific release
|
||||
</p>
|
||||
<p>
|
||||
Corresponds to the <code>source</code> attribute for the ant
|
||||
<a href="http://jakarta.apache.org/ant/manual/CoreTasks/javac.html">javac</a>
|
||||
task.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.iutest.dest</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the integration unit test classes directory.
|
||||
This is the location where the java classes for the
|
||||
integration unit test source code will be generated to.
|
||||
The default value is
|
||||
<code>${maven.build.dir}/iutest-classes</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.iutest.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the integration unit test source directory.
|
||||
This property should never be overridden as the value is
|
||||
determined directly from the project descriptor. The
|
||||
default value is
|
||||
<code>${maven.integrationUnitTestSourceDirectory}</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.out.test.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the directory where the integration unit testing
|
||||
is run. The default value is <code>${build.dir}/iutest</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.webapp.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the directory of the web application used to
|
||||
perform integration unit testing. The default value is
|
||||
<code>${iutest.dir}/testapp</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.conf.test.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the configuration directory used to build the
|
||||
web application used for integration unit testing. The
|
||||
default value is <code>${iutest.dir}/cactus</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.tomcat.home</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies your local Tomcat installation directory.
|
||||
The default value is <code>${tdk.home}</code>. If
|
||||
<code>${tdk.home}</code> is not specified in your
|
||||
<code>${user.home}/build.properties</code>, you should set
|
||||
this property. This is used for the integration unit
|
||||
testing.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.test.port</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies the port that Tomcat will use for integration
|
||||
unit testing. The default value is <code>8192</code>.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
</body>
|
||||
</document>
|
||||
Reference in new issue
Block a user