Starting in Maven 3.1.x, logging was switched to SLF4J
. The consequence is that you no longer receive DEBUG
or TRACE
logging messages in a cargo
build.
You can update ${MAVEN_HOME}/conf/logging/simplelogger.properties
. But that will create a lot of "noise."
org.slf4j.simpleLogger.defaultLogLevel=DEBUG
Instead, add the following entry to simplelogger.properties
.
org.slf4j.simpleLogger.log.org.codehaus.cargo.maven2.ContainerRunMojo=debug
Alternatively, you can create .mvn/jvm.config
. E.g.
cat ~/.mvn/jvm.config
-Dorg.slf4j.simpleLogger.log.org.codehaus.cargo.maven2.ContainerRunMojo=debug
Note: You may also set the logging level to trace
.
org.slf4j.simpleLogger.defaultLogLevel=info
org.slf4j.simpleLogger.showDateTime=false
org.slf4j.simpleLogger.showThreadName=false
org.slf4j.simpleLogger.showLogName=false
org.slf4j.simpleLogger.logFile=System.out
org.slf4j.simpleLogger.cacheOutputStream=true
org.slf4j.simpleLogger.levelInBrackets=true
org.slf4j.simpleLogger.log.Sisu=info
org.slf4j.simpleLogger.warnLevelString=WARNING
# MNG-6181: mvn -X also prints all debug logging from HttpClient
# Be aware that the shaded packages are used
# org.apache.http -> org.apache.maven.wagon.providers.http.httpclient
org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off
org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off