wildfly/wildfly-core — pull request #378 by jamezp (2014-12-04 18:53:13+00:00)
Title: [WFCORE-267] Default to the jboss-logmanager for the client JAR with a default configuration

This needs an okay from @aloubyansky and replaces https://github.com/wildfly/wildfly-core/pull/347.

Adds the jboss-logmanager to the `jboss-cli-client.jar`. The size addition is about 300k so not too bad.

The issue is when launching the jar and no log manager is configured the default JUL configuration is used which logs to the console by default. What this commit does is makes the `org.jboss.logmanager.LogManager` the default log manager if one was not already set. It also attempts to configure some defaults if the `jboss.cli.log.level` system property is set to any level but `OFF`.

Examples
```
java -jar ${JBOSS_HOME}/bin/client/jboss-cli-client.jar -Djboss.cli.log.level=INFO -Djboss.cli.log.file=${JBOSS_HOME}/jboss-cli.log

java -jar ${JBOSS_HOME}/bin/client/jboss-cli-client.jar -Djboss.cli.log.level=INFO
```

Leaving off the `-Djboss.cli.log.level` property will not configure a log manager so nothing will be logged to the console or a file.

This will also allow the `logging.configuration` property to be set or placing a `logging.properties` on the class path to override the defaults and use your own configuration file.