MetricsServiceProducer should not log "Using a backend implementation of null"
when backend implementation is chosen by default.
Slim down UI Console WAR

From 43MB to 8MB

The proper way to exclude webapp resources when copying them to
the target directory is to use the 'warSourceExcludes' tag

Besides, now all resources useless at runtime are listed.

Also, don't pollute the WEB-INF directory with an empty classes directory.
Merge pull request #60 from tsegismont/slimDownConsoleWar

Slim down UI Console WAR
Let the developer configure desired logging with system properties

Now by default, Wildfly logs at ERROR level in the CONSOLE and DEBUG level in
the project.build.directory/test.log file.

For this to happen, we need to copy a the /src/test/wildfly-resources file (filtered)
to the Wildfly standalone configuration directory during the process-test-classes phase.

Example:
mvn verify -Dwildfly.logging.console.level=DEBUG

Also:
* removed useless <id>Memory-backend</id> profile definition (it is the default)
* removed redundant info in Cassandra-backend profile
rhq-metrics dockerfile with readme.
Merge branch 'master' of https://github.com/rhq-project/rhq-metrics
changing .md to .adoc
Update README.adoc

sorry, br removed.
Merge pull request #59 from tsegismont/restTestLogging

Let the developer configure desired logging with system properties
Add debug logging (will be useful for tracking issue #57)
Fix InfluxTest: '30sec' is not a valid duration format

'30s' is a valid one.

The RestHandler was thus looking for metrics since epoch.
Not a big deal with this test case, as we expect the backend
to select all the metrics anyway.
Initial support of collectd in ptrans
Minor: use non-confusing variable names when setting up collectd
Make collectd listen port configurable
Set collectd default port in ptrans.properties
Merge pull request #51 from tsegismont/collectd-ptrans

Initial support of collectd in ptrans
Log Rest Test messages at DEBUG level in the console
ptrans: added "new config-file" parameter
ptrans logging: use bundled log4j.xml in production, log4j-dev.xml in development

Bundled log4j.xml outputs everything to stdout, at INFO level

Users who want to customize logging may specifiy a path
to a log4j configuration file with the 'log4j.configuration'
system property
ptrans: shutdown cleanly when the VM receives the TERM signal