WARNING: Full plugin rewrite! Version 3.0 of the Cactus plugin now relies on the newest Cactus/Ant integration which has completely changed since version 2.0 (and 2.1-SNAPSHOT, which by the way has never been released, and never will). Thanks to the new Cactus/Ant, some features have also been added. The plugin now uses the new <cactifywar> and <cactus> Ant tasks (see http://jakarta.apache.org/cactus/integration/ant/index.html for more details).
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113436 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
1 parent
fa22f63625
commit
eef02557cb
16 files changed
+527
-224
No files matched your search
@@ -7,15 +7,12 @@
|
||||
|
||||
<body>
|
||||
|
||||
<release version="2.1" date="in CVS">
|
||||
<release version="3.0" date="in CVS">
|
||||
<action dev="vmassol" type="update">
|
||||
Updated to use the Cactus/Ant integration built on 26th of April 2003.
|
||||
This makes the <code>web.xml</code> merge works.
|
||||
Major change: updated to use the Cactus/Ant integration built on
|
||||
23rd of May 2003 (it is completely different from the Cactus/Ant
|
||||
integration used in version 2.0.
|
||||
</action>
|
||||
<action dev="bwalding" type="fix">
|
||||
Fix bug where generation of the Cactus report was failing in some
|
||||
cases.
|
||||
</action>
|
||||
</release>
|
||||
|
||||
<release version="2.0" date="2003-04-08">
|
||||
|
||||
@@ -8,6 +8,19 @@
|
||||
</properties>
|
||||
<body>
|
||||
<goals>
|
||||
<goal>
|
||||
<name>cactus:compile</name>
|
||||
<description>
|
||||
Compiles the Cactus tests.
|
||||
</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>cactus:cactifywar</name>
|
||||
<description>
|
||||
Creates a Cactus-ready war from the application war (depends
|
||||
on <code>war:war</code>).
|
||||
</description>
|
||||
</goal>
|
||||
<goal>
|
||||
<name>cactus:test</name>
|
||||
<description>
|
||||
|
||||
+145
-35
@@ -21,9 +21,9 @@
|
||||
<p>
|
||||
Home directory of where you have installed the container on
|
||||
which you wish to run the Cactus tests. Valid container
|
||||
names are: <code>tomcat4x</code>, <code>resin2x</code>,
|
||||
<code>orion1x</code>, <code>weblogic6x</code>,
|
||||
<code>weblogic7x</code> and <code>jboss3x</code>.
|
||||
names are: <code>tomcat4x</code>, <code>tomcat5x</code>,
|
||||
<code>resin2x</code>, <code>orion1x</code>,
|
||||
<code>orion2x</code> and <code>jboss3x</code>.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -47,16 +47,6 @@
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.target.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location where the plugins puts temporary build-generated
|
||||
files. Default value is <code>${maven.build.dir}/cactus</code>.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.src.includes</td>
|
||||
<td>Yes</td>
|
||||
@@ -77,17 +67,6 @@
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.context</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Name of the webapp context under which the application will be
|
||||
deployed for executing the Cactus tests. Default
|
||||
value is <code>cactustest</code>.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.junit.usefile</td>
|
||||
<td>Yes</td>
|
||||
@@ -130,6 +109,22 @@
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.src.mergewebxml</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of a test-specific web.xml file that will be merged with
|
||||
the application web.xml, during the War cactification. Note that
|
||||
by default the cactification already adds the Cactus redirector
|
||||
definitions.Decides whether to stop the build on test failures.
|
||||
Example:
|
||||
<code>cactus.src.mergewebxml = ${basedir}/src/conf/cactus-web.xml</code>.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<!--
|
||||
<tr>
|
||||
<td>cactus.runner</td>
|
||||
<td>Yes</td>
|
||||
@@ -140,26 +135,17 @@
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
-->
|
||||
</table>
|
||||
</section>
|
||||
|
||||
<section name="Cactus/JBoss Settings">
|
||||
<section name="Cactus/JBoss 3.x Settings">
|
||||
<table>
|
||||
<tr>
|
||||
<th>Property</th>
|
||||
<th>Optional?</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.jboss3x.config.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of the JBoss server configuration directory.
|
||||
Default value is <code>${cactus.home.jboss3x}</code>.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.jboss3x.config.name</td>
|
||||
<td>Yes</td>
|
||||
@@ -172,6 +158,130 @@
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
|
||||
<section name="Cactus/Resin 2.x Settings">
|
||||
<table>
|
||||
<tr>
|
||||
<th>Property</th>
|
||||
<th>Optional?</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.resin2x.config</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of the Resin 2.x configuration file if you don't want
|
||||
to use the cactus-provided one.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
|
||||
<section name="Cactus/Tomcat 4.x Settings">
|
||||
<table>
|
||||
<tr>
|
||||
<th>Property</th>
|
||||
<th>Optional?</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat4x.config</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of the Tomcat 4.x configuration file if you don't want
|
||||
to use the cactus-provided one.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat4x.conf.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of custom Tomcat 4.x configuration file that will be
|
||||
copied, overwriting the Cactus-provided configuration files.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat4x.conf.includes</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Configuration files located at
|
||||
<code>${cactus.tomcat4x.conf.dir</code> that should be included
|
||||
in the Tomcat 4.x container set up by Cactus.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat4x.conf.excludes</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Configuration files located at
|
||||
<code>${cactus.tomcat4x.conf.dir</code> that should not be
|
||||
included in the Tomcat 4.x container set up by Cactus.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
|
||||
<section name="Cactus/Tomcat 5.x Settings">
|
||||
<table>
|
||||
<tr>
|
||||
<th>Property</th>
|
||||
<th>Optional?</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat5x.config</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of the Tomcat 5.x configuration file if you don't want
|
||||
to use the cactus-provided one.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat5x.conf.dir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Location of custom Tomcat 5.x configuration file that will be
|
||||
copied, overwriting the Cactus-provided configuration files.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat5x.conf.includes</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Configuration files located at
|
||||
<code>${cactus.tomcat5x.conf.dir</code> that should be included
|
||||
in the Tomcat 5.x container set up by Cactus.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cactus.tomcat5x.conf.excludes</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
Configuration files located at
|
||||
<code>${cactus.tomcat5x.conf.dir</code> that should not be
|
||||
included in the Tomcat 5.x container set up by Cactus.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
|
||||
</body>
|
||||
</document>
|
||||
@@ -12,7 +12,7 @@
|
||||
Lists of todos and ideas for future versions.
|
||||
</p>
|
||||
|
||||
<subsection name="2.1">
|
||||
<subsection name="3.1">
|
||||
<p>
|
||||
<ul>
|
||||
<li>
|
||||
|
||||
@@ -19,17 +19,18 @@
|
||||
Create a <code>build.properties</code> file in your project root
|
||||
directory (where <code>project.xml</code> is located) and define in
|
||||
it the location of the container you wish to use for the tests. For
|
||||
example, if you wish to run the Cactus tests on Tomcat 4.1.10 and on
|
||||
Resin 2.4, you will write:
|
||||
example, if you wish to run the Cactus tests on Tomcat 4.1.24 and on
|
||||
Resin 2.6, you will write:
|
||||
</li>
|
||||
|
||||
<source><![CDATA[
|
||||
cactus.home.tomcat4x = C:/Apps/jakarta-tomcat-4.1.10
|
||||
cactus.home.resin2x = C:/Apps/resin-2.1.4
|
||||
cactus.home.tomcat4x = C:/Apps/jakarta-tomcat-4.1.24
|
||||
cactus.home.resin2x = C:/Apps/resin-2.1.6
|
||||
]]></source>
|
||||
|
||||
<li>
|
||||
Then, simply type <code>maven cactus:test</code> to run the Cactus
|
||||
Then, simply type <code>maven cactus:test</code> (or
|
||||
<code>maven cactus</code> for short) to run the Cactus
|
||||
tests.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
Reference in new issue
Block a user