[ANN] Maven Surefire Plugin 2.11 Released

[Kristian Rosenvold <kr...@gmail.com>]

The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.11


This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
creating the web interface version of the test results, as well as the
maven-failsafe-plugin, which executes the integration tests of an
application.

This version supports JUnit 4.8 @Category annotation, using the
"groups" parameter on the plugin (using the 4.7 provider).

The other new feature in this release are runOrder="failedfirst" and
runOrder="balanced", this last parameter tries to optimize the overall
run-time for parallel test runs.


Users migrating from "classic" JUnit4 to the 4.7 provider to use
categories may want to take note of
http://jira.codehaus.org/browse/SUREFIRE-798

Users having troubles running with forkMode="never" for 2.9 and 2.10 may
want to take note of
http://jira.codehaus.org/browse/SUREFIRE-<http://jira.codehaus.org/browse/SUREFIRE-798>
801.

Changes to the proposed Surefire API are documented in the API page
http://maven.apache.org/plugins/maven-surefire-plugin/api.html

This version is marked as the last java 1.4 compatible version, the next
version will
be java 1.5. Surefire can still *fork* all the way down to jdk 1.3 for
JUnit 3.8.1.

http://maven.apache.org/plugins/maven-surefire-plugin/

http://maven.apache.org/plugins/maven-failsafe-plugin/

You should specify the version in your project's plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.11</version>
</plugin>


Release Notes - Maven Surefire - Version 2.11



** Bug
    * [SUREFIRE-508] - cannot run GWTTestCases with surefire
    * [SUREFIRE-549] - TestNg provider does not run junit tests
correctly when forkMode=always
    * [SUREFIRE-746] - Other registered failing RunListeners cause
NullPointerException in ConcurrentReporterManager, falsely report of
"No tests were executed!":
    * [SUREFIRE-760] - mvn -Dtest=ClassName#methodName does not work
with parallel tests
    * [SUREFIRE-775] - ForkingRunListener throws ArrayIndexOutOfBoundsException
    * [SUREFIRE-777] - Wrong default name for Failsafe Report
    * [SUREFIRE-780] - Success claimed when jvm fails to launch
    * [SUREFIRE-782] - Wrong links on surefire-plugin page
    * [SUREFIRE-785] - Lots of newlines being strewn about in test output
    * [SUREFIRE-786] - JUnit @Category are not taken into account if
forkMode=always
    * [SUREFIRE-787] - Test fail cause message is badly displayed if
exception message conatins line feeds
    * [SUREFIRE-791] - JUnit47 provider reports incorrect elapsed time
on test failure.
    * [SUREFIRE-793] - JUnit47 provider reports incorrect time in the XML report
    * [SUREFIRE-801] - Classloading compatibility break with
forkMode=NEVER in 2.9 and 2.10


** Improvement
    * [SUREFIRE-518] - Do not generate empty ouput files when
redirectTestOutputToFile is enabled
    * [SUREFIRE-611] - surefire exit code should explicitly
distinguish between crashed and failed unit test(s)
    * [SUREFIRE-772] - [Report Goal] Skip Maven Failsafe Report

** New Feature
    * [SUREFIRE-656] - JUnit 4.8 @Category support
    * [SUREFIRE-795] - There should be a way to balance tests across threads

** Story
    * [SUREFIRE-784] - Surefire plugin cannot be debugged remotely by eclipse

** Task
    * [SUREFIRE-802] - Dcoument Surefire API changes


** Wish
    * [SUREFIRE-329] - Support for JUNIT extensions

Enjoy,

-The Maven team