[ https://issues.redhat.com/browse/WFCORE-5115?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-5115: ---------------------------------- Description: With the fix for [generating a {{logging.properties}} config|https://github.com/wildfly-extras/wildfly-jar-maven-plugin/issues/73] there is a chance properties defined in the {{system-properties}} or {{path}} resource may be needed for the log manager at boot. As part of the mentioned fix a {{boot-config.properties}} file will be generated. The entry point of the bootable JAR should look for this file in the {{$JBOSS_HOME/standalone/configuration}} directory and if found load those system properties before the log manager is configured. (was: With the fix for [generating a {{logging.properties}} config|https://github.com/wildfly-extras/wildfly-jar-maven-plugin/issues/73] there is a chance properties defined in the {{system-properties}} or {{path}} resource may be needed for the log manager at boot. As part of the mentioned fix a {{boot-config.properties}} file will be generated. The entry point of the bootable JAR should look for this file in the {{$JBOSS_HOME/standalone/configuration}} directory and if found load those system properties before the log manager is configured. Properties passed to via the command line should take precedence over these defined properties as well.) -- This message was sent by Atlassian Jira (v7.13.8#713008)