You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Christoph Läubrich (Jira)" <ji...@apache.org> on 2022/07/29 15:53:00 UTC

[jira] [Created] (MNG-7525) Automatic handling of non multi thread safe mojos

Christoph Läubrich created MNG-7525:
---------------------------------------

             Summary: Automatic handling of non multi thread safe mojos
                 Key: MNG-7525
                 URL: https://issues.apache.org/jira/browse/MNG-7525
             Project: Maven
          Issue Type: Improvement
            Reporter: Christoph Läubrich


Currently, when I run a mojo that is not marked as thread safe, one gets a warning from maven. The usual "workaround" is to ask the mojo author to add a global lock and mark the mojo as thread safe, but this is rather useless, because the Mojo obviously not became "thread-safer", requires additional code and release ...

It would be better if maven handle this internally e.g. simply synchronize on the mojo-class-object  when executing a mojo that is not marked as thread-safe.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)