I've encountered an issue with the micronaut-maven-plugin where it outputs unnecessary log information, regardless of the Maven command being executed. This behavior persists even when using Maven's quiet mode (-q).
Issue Description:
Regardless of the specific Maven command being run, micronaut-maven-plugin always prints an additional log message that seems unnecessary for the operation being performed. Specifically, the log message is:
[info] Cannot find Micronaut Test Resources service settings, server may already be shutd
eg:
mvn help:evaluate -Dexpression=project.version -q -DforceStdout
0.6-SNAPSHOT[info] Cannot find Micronaut Test Resources service settings, server may already be shutdown.
This message appears even for commands that should not initiate or interact with any test resources or server operations, such as mvn help:evaluate -Dexpression=project.version -q -DforceStdout.
Expected Behavior:
The expected behavior is that the plugin should either respect Maven's logging levels (including quiet mode) or provide a configuration option to suppress such informational logs that are not relevant to the execution context. Test Resources should be only "called" on test maven goal, not for all goals.
I've encountered an issue with the micronaut-maven-plugin where it outputs unnecessary log information, regardless of the Maven command being executed. This behavior persists even when using Maven's quiet mode (-q).
Issue Description: Regardless of the specific Maven command being run, micronaut-maven-plugin always prints an additional log message that seems unnecessary for the operation being performed. Specifically, the log message is:
eg:
This message appears even for commands that should not initiate or interact with any test resources or server operations, such as mvn help:evaluate -Dexpression=project.version -q -DforceStdout.
Expected Behavior: The expected behavior is that the plugin should either respect Maven's logging levels (including quiet mode) or provide a configuration option to suppress such informational logs that are not relevant to the execution context. Test Resources should be only "called" on
test
maven goal, not for all goals.I used
and I'm sure that issue was not present in previews versions.