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