; dependency, war...
> Would all of these patched maven plugins been planned in the next Maven
> (components and default-bindings) release as well?
>
>
>
> -
> BR, tibor17
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Important-Not
://maven.40175.n5.nabble.com/Important-Notice-for-all-users-of-the-parallel-build-feature-tp5809947p5810008.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
The testcase was supplied by Chris Rompot in
http://jira.codehaus.org/browse/MASSEMBLY-684
The test failed with sufficiently high frequency that I could "easily"
track down the problem in a day or so.
The bug is twofold; it regards overlapping calls to Method#setVisible
between different threads,
Additionally, this issue affects parallel artifact download/pom
interpolation in maven core. The overall symptom is interpolation
expressions like ${project.name} not being resolved, but this can lead
to interesting kinds of corruption.
The fix can be applied to all 3.x versions of maven by droppi
As can be seen from https://jira.codehaus.org/browse/PLXCOMP-258, all
the related issues are marked as "fixed", which means the fix will be
part of the next release of all the components in question. Given the
number of components involved, this will take a bit of time..
Kristian
2014-10-18 20:42
Is it possible to include this jar to maven distribution? Because it is not
always possible to change it on build servers .
On 19 October 2014 01:22, Kristian Rosenvold
wrote:
> Thanks to an excellent testcase provided by a JIRA user, a significant
> source of thread safety bugs has been loc
Kristian,
Where can I find the test case and more information about the problem
and the fix? Thank you in advance.
--
Regards,
Igor
On 2014-10-18, 14:22, Kristian Rosenvold wrote:
Thanks to an excellent testcase provided by a JIRA user, a significant
source of thread safety bugs has been locat
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 paral
