Falko Modler created MNG-7380:
---------------------------------
Summary: Don't log non-threadsafe warning if only building a
single module
Key: MNG-7380
URL: https://issues.apache.org/jira/browse/MNG-7380
Project: Maven
Issue Type: Improvement
Components: Plugins and Lifecycle
Affects Versions: 3.8.4
Reporter: Falko Modler
When building a _single_ module (via {{-f}}, {{-pl}} or simply cd'ing into it)
with e.g. {{-T1C}} in {{.mvn/maven.config}} logs a warning if a non-threadsafe
mojo is executed, e.g.:
{noformat}
[WARNING] *****************************************************************
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that have goals not marked *
[WARNING] * as @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates *
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in *
[WARNING] * question, not against maven-core *
[WARNING] *****************************************************************
[WARNING] The following plugins are not marked @threadSafe in code-with-quarkus:
[WARNING] io.quarkus.platform:quarkus-maven-plugin:2.6.1.Final
[WARNING] Enable debug to see more precisely which goals are not marked
@threadSafe.
[WARNING] *****************************************************************
{noformat}
This is unnecessary noise because with only a single module there can never be
a concurrency issue, no matter how many threads are enabled.
Maven should check if it's building only one module before logging this warning.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
