[MNG-7525] Automatic handling of non multi thread safe mojos

**[Christoph Läubrich](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=laeubi)** opened **[MNG-7525](https://issues.apache.org/jira/browse/MNG-7525?redirect=false)** and commented

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.

---

1 votes, 1 watchers

No files, tests, or entry points are named. Start by tracing Maven core's mojo execution path for mojos not marked thread-safe, then evaluate the proposed synchronization on the mojo class object. Done means non-thread-safe mojos are handled internally without requiring plugin changes, with concurrency behavior covered by tests.

Written by the indexing model from the issue text.