maven.compile.target
and
maven.compile.source
properties.
jvmArgs
property to the containers tasks.
source
attribute from the java plugin for
compiling cactus tests.
WEB-INF/classes
), through the use of variable
cactus.resources.dirs
.
cactus.sysproperties
property to the
cactus:match
and cactus:single
goals.
cactus:test
is not executed if property
maven.test.skip
is set.
maven.war.build.dir
,
maven.war.final.name
, maven.ejb.build.dir
and maven.ejb.final.name
properties from the WAR and EJB
plugins instead of hard-coding the values. Note that as a result, the
Cactus plugins now requires version 1.7+ of the WAR plugin and version
1.6+ of the EJB plugin.
cactus.jboss3x.config.dir
property which allows
users to specify the location of a custom JBoss server configuration
to use. This configuration, if specified, will be copied by the
<cactus> task to cactus.jboss3x.tmp.dir
.
cactus.jboss3x.tmp.dir
property which
points to where the JBoss server configuration for Cactus will be
created. It defaults to
${cactus.home.jboss3x}/server/cactus
.
cactus.sysproperties
property to the
Maven plugin for Cactus to allow passing system properties to
the client and server side Cactus JVMs.
cactus:test
, only run the tests if there are
Cactus tests present in the filesystem (i.e. if the Cactus source
directory exists).
commons-jelly-tags-xml
. It seems
this is required for some configurations of Maven.
cactus:test
can now also be used to run tests packaged
in an EAR. However the cactus.is.ear
property needs
to be set to true
(it is false
by default
thus packaging tests in a WAR).
<ear.module>
property tagging +
support for sar modules + fixes a bug in the generation of the EAR
descriptor.
cactus:test-ear
goal was not using properly the
cactus.test.includes
/cactus.test.excludes
thus
leading to tests not being included/excluded.
cactus:test-ear
goal) with the behavior from the EAR Maven
plugin. More specifically the Cactus plugin now honors both the
<ear.bundle>
property tagging, the
maven.ear.src
property and the
maven.ear.manifest
property.
project.xml
.
cactus:test-ear
, do not include the EJB sources in
the cactified WAR inside the EAR we deploy.
cactus.jboss3x.jndiport
property to specify
which JNDI port to use when shutting down JBoss. Defaults to 1099
(the JBoss default).
cactus.logging.config.client
and
cactus.logging.config.server
. They point to logging
config properties file.
cactus.src.war
and
cactus.src.ejb
properties to specify where to find the
artifacts to test using Cactus.
cactus.build.goal.war
and
cactus.build.goal.ejb
) for defining which goal is called
by Cactus to generate the war and ejb artifacts. They default to
war:war
and ejb:ejb
respectively.
cactus.war
property. It specified the
location where to generate the cactified WAR. Note that this is
also the name of the test context that will be used (except if
the context is specified by other means such as in
application.xml
if the WAR is packaged in an EAR,
etc). It defaults to
${maven.build.dir}/${pom.artifactId}-cactus.war
.
configxml
attribute used in the
<weblogic7x>
element of the
<cactus>
task.
cactus:test-ear
packages the whole thing in an EAR and
executes the Cactus tests.
cactus:test
goal now automatically discovers JUnit
Test Cases from non JUnit java classes and by default excludes all
classes that are not tests.
cactus.src.includes
and
cactus.src.excludes
in cactus.test.includes
and cactus.test.excludes
. The previous names were
misleading and some Cactus useres thought it referred to
inclusion/exclusion of classes during the compilation. Please also note
that files to include/exclude are now .class
files and no
longer .java
files.
${maven.war.final.name}
property instead of hard-coding the war name to
${pom.artifactId}.war
.