Only prefix program output with thread name when running with multiple threads #157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to some review comments in Pull Request #153 (for Issue #152) after it had been merged.
Attaching the owning thread name to program output as a prefix will only occur if the Maven session is running with 2 or more threads (i.e.
session.isParallel()
). Otherwise no log prefix is attached.Examples
Below is sample output of two modules in a reactor with the following plugin execution configured:
Example 1. Default behavior, single-thread:
mvn clean install
Example 2. Default behavior, multi-thread:
mvn clean install -T 2
Example 3. With Maven Logger option enabled, single-thread:
mvn clean install -Dexec.useMavenLogger=true
Example 4. With Maven Logger option enabled, multi-thread:
mvn clean install -T 2 -Dexec.useMavenLogger=true
NOTE: In these last 2 examples, My Maven installation is configured to always print timestamp and thread name before Maven log output.