Hi. I don't know whether this issue is related to #6 or not.
However, I have Maven modules that depend on libraries using SLF4j. And when I run mvn clean cobertura:cobertura on these modules, I see a lot of DEBUG outputs. Most of them are related to my dependencies. But, it seems Cobertura's LOG4j configuration overrides my global configuration.
So, said differently, when using the Cobertura plug-in in version 2.7 with my project, some modules display DEBUG logs they should not. The quiet property does not change anything. Swicthing back to the Cobertura plug-in 2.6 solves the issue (debug messages are not shown anymore).
Hi. I don't know whether this issue is related to #6 or not. However, I have Maven modules that depend on libraries using SLF4j. And when I run
mvn clean cobertura:cobertura
on these modules, I see a lot of DEBUG outputs. Most of them are related to my dependencies. But, it seems Cobertura's LOG4j configuration overrides my global configuration.So, said differently, when using the Cobertura plug-in in version 2.7 with my project, some modules display DEBUG logs they should not. The quiet property does not change anything. Swicthing back to the Cobertura plug-in 2.6 solves the issue (debug messages are not shown anymore).