Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated some details

...

This depends greatly on your module structure, but the following observations have been made:

  • 20-40% 50% speed improvement is quite common.
  • Distributing tests among your modules is likely to improve performance, putting all your tests in one module decreases it - unless you
    run one of the parallel surefire test providers.
  • Running tests in parallel within a single surefire-instance is a little different from running multiple surefire-runs (from separate projects),
    since there will be different classloaders. Remember that tcp/ip ports and files are still singletons.
  • For builds with evenly distributed tests (in the modules), weave mode has an advantage over parallel mode.
  • When running with -DskipTests, the difference between parallel and weave tends to be marginal.

...

  • Surefire with forkMode=never, surefire [2.6,) asserts this.
  • maven-modello-plugin (, fixed in svn trunk, upcoming [1.4,)There is a bug in plexus io (on non windows machines) that causes all the jar/war/ear plugins to intermittently fail with output on the form "Failed to retrieve numeric file attributes using: '/bin/sh -c "ls -1nlaR <a path>". This can be fixed by upgrading to the latest xAR plugins
  • All non-threadsafe xAR plugins (war, jar, ear etc); fixed in latest released versions.

Known non-thread safe libraries

Known thread safety problems have been fixed in the following library versions:

plexus-utils 2.0.5
maven-archiver 2.4.1
plexus-archiver 1.0
plexus-io 1.0

Known issues

It is not required to report jiras for these issues:

...

This checklist qualifies for a "simple thread safety" review of a mojo.

Known non-thread safe libraries

Known thread safety problems have been fixed in the following library versions:

plexus-utils 2.0.5
maven-archiver 2.4.1
plexus-archiver 1.0
plexus-io 1.0
modello (1.4-SNAPSHOT, 1.3 does not work)