Since version 1.7.1 of Cactus all changes are now recorded using Apache's JIRA. The list of changes for an unreleased version is available in the JIRA roadmap report and the released version changes in the JIRA changelog report. Proper use of maven.compile.target and maven.compile.source properties. Added jvmArgs property to the containers tasks. Added optional source attribute from the java plugin for compiling cactus tests. Allows Cactus to include some resources in the webapp classpath (WEB-INF/classes), through the use of variable cactus.resources.dirs. Updated AspectJ to 1.2.1, so Cactus compiles and run under JDK 1.5. Extended cactus.sysproperties property to the cactus:match and cactus:single goals. Goal cactus:test is not executed if property maven.test.skip is set. Cactus now uses HttpUnit 1.6. Plugin is now buildable withouth any manual intervention. The Cactus HTML JUnit report now displays the stack trace in case of failure. The plugin now correctly uses the 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 now guesses automatically what Java source files are Cactus tests when packaging tests in an EAR (it was already supported when running tests packaged in a WAR). Added new 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. Added new 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. Added new cactus.sysproperties property to the Maven plugin for Cactus to allow passing system properties to the client and server side Cactus JVMs. When calling cactus:test, only run the tests if there are Cactus tests present in the filesystem (i.e. if the Cactus source directory exists). Added dependency on commons-jelly-tags-xml. It seems this is required for some configurations of Maven. Removed explicit dependencies on EAR and WAR plugins so that users are free to install the versions they want to work with. As it was, we were forcing them to use a specific version, which is bad. The 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). Aligning the EAR-ing behavior in the Cactus plugin for Maven with the behavior from the EAR Maven plugin. More specifically, supports the new <ear.module> property tagging + support for sar modules + fixes a bug in the generation of the EAR descriptor. The cactus:test-ear goal was not using properly the cactus.test.includes/cactus.test.excludes thus leading to tests not being included/excluded. Updated the version of Commons HttpClient in the Cactus distribution to 2.0 final. Aligned the EAR-ing behavior in the Cactus plugin (when using the 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. Added support for running tests packaged as an EAR when the Cactus plugin is triggered by defining the Cactus report in project.xml. When running Cactus tests on an EJB project, through cactus:test-ear, do not include the EJB sources in the cactified WAR inside the EAR we deploy. Added new cactus.jboss3x.jndiport property to specify which JNDI port to use when shutting down JBoss. Defaults to 1099 (the JBoss default). Added support for Resin 3.x (above version 3.0.5). Added support for custom ports when using JBoss. Please note that this will only work with custom JBoss configs. The default config used by Cactus uses port 8080 (that's the default JBoss config). Added 2 new properties to support debugging Cactus tests: cactus.logging.config.client and cactus.logging.config.server. They point to logging config properties file. Added new optional cactus.src.war and cactus.src.ejb properties to specify where to find the artifacts to test using Cactus. Added 2 properties (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. Added new optional 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. Added support for the new configxml attribute used in the <weblogic7x> element of the <cactus> task. Added support for EJB testing with Cactus. Calling cactus:test-ear packages the whole thing in an EAR and executes the Cactus tests. The cactus:test goal now automatically discovers JUnit Test Cases from non JUnit java classes and by default excludes all classes that are not tests. Renamed properties 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. When running reports, make sure Cactus tests do not fail the build. Fixed bug MAVEN-1000. Cactus tests are now automatically started by default when the site is generated. This feature can be turned off. The plugin now correctly uses the ${maven.war.final.name} property instead of hard-coding the war name to ${pom.artifactId}.war. Moved the Cactus plugin from the Maven CVS to the Cactus CVS.