Yes. I think so. Based on my observations, that is my current understanding, anyway. If you eventually figure out how to do that configuration/disabling — which I haven’t figured out how to do yet — please don’t hesitate to correct my assumption.
Another option is to verify your plugin’s logging using a TestKit functional test. If you set the GradleRunner to forwardOutput( )…
GradleRunner.create( )
...
.forwardOutput( )
...
…and given you do some logging in your plugin, when you run your functional test, then you could assert that your plugin is logging whatever you’re expecting…
...
result.output.contains( "whatever you're expecting" )
...
Whatever you end up going with, please share your eventual solution with the rest of us enquiring minds? TIA 