You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-Dmvnd.log.level=DEBUG works as expected, but building without -Dmvnd.log.level=DEBUG (as expected per logback docs) leads to org.jboss.fuse.mvnd being set to DEBUG anyway, which is not nice.
The text was updated successfully, but these errors were encountered:
I found what is happening. The daemon JVM is launched first without any specific system properties from the command line, so when the logback configuration is loaded, the mvnd.log.level is not set.
The workaround is to use mvnd.jvmArgs="-Dmvnd.log.level=DEBUG" in one of the mvnd.properties file or on the command line using -Dmvnd.jvmArgs="-Dmvnd.log.level=DEBUG". Note that the mvnd.jvmArgs is a discriminating property, so a specific daemon will be created.
I wanted to add something like the following to logback.xml, but it does not work
With the above setting and
-Dmvnd.log.level=DEBUG
passed via CLI, the log level is not set toDEBUG
.When I change it to
-Dmvnd.log.level=DEBUG
works as expected, but building without-Dmvnd.log.level=DEBUG
(as expected per logback docs) leads toorg.jboss.fuse.mvnd
being set toDEBUG
anyway, which is not nice.The text was updated successfully, but these errors were encountered: