[MNG-7380] Don't log non-threadsafe warning if only building a single module

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.8.4
• Fix Version/s: 3.8.5, 4.0.0-alpha-2, 4.0.0
• Component/s: Plugins and Lifecycle
• Assignee: Michael Osipov
• Reporter: Falko Modler
• Created: 30/Dec/21 00:45
• Updated: 20/Oct/22 08:11
• Resolved: 11/Jan/22 14:54

Description

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.:

[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] *****************************************************************

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.

Issue Links

• links to: GitHub Pull Request #655