Merge pull request #185 from jmxtrans/configuration-format-change

Change configuration format to get rid of settings on OutputWriters
Remvoed live check on Sockets.

This check is problematic as it waits 100[ms] for a timeout, which is a very, very long time once you have some traffic.

This PR might fix #123 andfix #190. Note the emphasis on the _might_. I've had similar problems with JMXTrans that have been fixed by removing this check, but I have not enough information on those issue to ensure this is the same problem.
Added unit test of JmxConnectionParams to validate hypothesis of issue #190.

Short story, seems that hashCode() implementation is good, at least in HEAD.
Added unit test of JmxConnectionParams to validate hypothesis of issue #190.

Also added tests for equals() method while I'm at it ...
Merge pull request #189 from jmxtrans/conversion-of-booleans-to-numbers-by-output-writers

Conversion from boolean to number implemented on OutputWriters.
Merge pull request #191 from jmxtrans/simplify-check-on-socket-factory

Remvoed live check on Sockets.
Merge pull request #192 from jmxtrans/jmx-remote-pool-not-reusing-connections

Added unit test of JmxConnectionParams to validate hypothesis of issue #190.
Make JMXConnectionParams.hashCode() and equals() robust to array environment values.

This is a very ugly workaround which fixes #190. To make sure arrays with same parameters are treated as equals, we convert them to lists in the hashCode and equals methods. We could improve performance by caching the result (environment is immutable) but as environment is expected to be small, the gain is probably not worth the additional complexity.
Merge pull request #193 from jmxtrans/jmx-remote-pool-not-reusing-connections

Make JMXConnectionParams.hashCode() and equals() robust to array environment values.
Fixed problem in reloading configuration
Merge pull request #198 from jmxtrans/fix-reload-of-configuration

Fixed problem in reloading configuration

Fix is simple enough, not waiting for additional reviews.
WIP - RPM packaging done with Maven

Packaging directly from Maven introduce quite a few benefits :

* versioning can be coherent between pom and RPM
 * RPM can be attached as build artifact and uploaded with the results of the build
 * Maven release plugin can be used to ensure coherence of releases
 * ...

Introduce appassembler maven plugin to integrate TanukiSoft java wrapper (because no Java daemon should be left behind).

Minimal RPM created from this. Not all functionality have been ported, some on purpose (GC tuning should probably be left to the end user, not much chance that generic optimizations make sense in all cases) some by ignorance (I'm not a very good packager).

Note that this is work in progress and needs comment / rework before merging.
Added documentation
Add yaml2jmxtrans, configuration files moved to more standard locations.

Based on comments from https://groups.google.com/forum/#!topic/jmxtrans/UuT2MsUcvps

Still problem with user creation.
Fixed user creation problem
Added Vagrant VM to build RPM (for the unlucky who do not work on Linux). "vagrant up" should start a VM, install dependencies and build the RPM. You should end up with the RPM under target/rpm/...