[ 
https://jira.codehaus.org/browse/MCOMPILER-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297884#comment-297884
 ] 

Falko Modler edited comment on MCOMPILER-170 at 5/4/12 12:23 PM:
-----------------------------------------------------------------

Thanks for the pointer, but I don't know whether I understood you correctly:

You mean this is a general problem and it is not specific for the changes that 
have been made for 2.4?
But why does everything work as expected in 2.3.2 then?

There was also no note of switching on the forking when @threadSafe was 
introduced, see: MCOMPILER-127

Btw: Switching on forking does indeed work around this issue but it also slows 
down the build a bit. And of course it can't benefit from MCOMPILER-166 either 
(which was the main reason for me to try 2.4).
                
      was (Author: famod):
    Thanks for the pointer, but I don't know whether I understood you correctly:

You mean this is a general problem and it is not specific for the changes that 
have been made for 2.4?
But why does everything work as expected in 2.3.2 then?

There was also no note of switching on the forking when @threadSafe was 
introduced, see: MCOMPILER-127

Btw: Switching on forking does indeed work around this issue but it also slows 
down the build a bit. And of course it can't benefit from MCOMPILER-166 either 
(which was the main reason for me the try 2.4).
                  
> 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

        

Reply via email to