[
https://jira.codehaus.org/browse/MCOMPILER-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297892#comment-297892
]
Olivier Lamy commented on MCOMPILER-170:
----------------------------------------
The optimization introduces by MCOMPILER-166 means we only use 1 instance of
Javac class instead of rebuild it for all compilation.
This Javac instance is not thread safe (euh we cannot fix that :-) ).
So sure the compiler plugin is not threadSafe if you don't fork compiler.
> Regression: Compiler Plugin fails when building with multiple threads (-T...)
> -----------------------------------------------------------------------------
>
> Key: MCOMPILER-170
> URL: https://jira.codehaus.org/browse/MCOMPILER-170
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows 7 x64, JDK 1.6.0_31, Maven 3.0.4
> Reporter: Falko Modler
> Priority: Critical
>
> I just tried building my current project which is rather large and has many
> sub-modules.
> With version 2.3.2 (and below) of the plugin I was able to build the whole
> project with multiple threads, let's say:
> {{mvn clean compile -T4}}
> Version 2.4 fails with random errors when using this command line!
> Errors include missing closing brackets, "cannot find symbol" and so on. It's
> also not always the same module where the errors occur.
> A single-threaded build with:
> {{mvn clean compile}}
> *completes just fine*!
> Unfortunately I cannot upload my project for copyright reasons.
> So for me it looks like a "classic" concurrency problem. Maybe side effect of
> MCOMPILER-166?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
