Prevent informational JMH messages for default Gradle log level #265
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently every JMH bytecode generation task run produces log messages like the following even if just the default "lifecycle" log level is being used. ``` > Task :jmhRunBytecodeGenerator Processing 0 classes from .../build/classes/java/jmh with "reflection" generator Writing out Java source to .../build/jmh-generated-sources and resources to .../build/jmh-generated-resources Processing 0 classes from .../build/classes/java/test with "reflection" generator Writing out Java source to .../build/jmh-generated-sources and resources to .../build/jmh-generated-resources ``` This change prevents these log messages unless Gradle's "info" (or finer grained) log level is being used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently every JMH bytecode generation task run produces log messages like the following even if just the default "lifecycle" log level is being used.
This change prevents these log messages unless Gradle's "info" (or finer grained) log level is being used.