Thanks to an excellent testcase provided by a JIRA user, a significant
source of thread safety bugs has been located and fixed. The problem
has an extensive reach, and can be the source of practically *any*
issue in parallel builds, and is probably the root cause of most JIRA
issues filed wrt parallel build problems.
Fortunately, there is a very simple fix by putting the following
inside your plugin configuration:
<plugin>
...
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-interpolation</artifactId>
<version>1.21</version>
</dependency>
</dependencies>
</plugin>
You should also put this jar file in the lib/ext folder of your maven
installation:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interpolation/1.21/plexus-interpolation-1.21.jar
Which plugins are affected ? It's almost easier to tell which is /not/
affected. See the "relates" link on
https://jira.codehaus.org/browse/PLXCOMP-258 to see which
plugins/tools are affected.
Kristian
source of thread safety bugs has been located and fixed. The problem
has an extensive reach, and can be the source of practically *any*
issue in parallel builds, and is probably the root cause of most JIRA
issues filed wrt parallel build problems.
Fortunately, there is a very simple fix by putting the following
inside your plugin configuration:
<plugin>
...
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-interpolation</artifactId>
<version>1.21</version>
</dependency>
</dependencies>
</plugin>
You should also put this jar file in the lib/ext folder of your maven
installation:
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interpolation/1.21/plexus-interpolation-1.21.jar
Which plugins are affected ? It's almost easier to tell which is /not/
affected. See the "relates" link on
https://jira.codehaus.org/browse/PLXCOMP-258 to see which
plugins/tools are affected.
Kristian