Allow client span names to be set based on pattern matching.

For instance, perhaps you want to have your client span names
reported as `/api/{userid}/update` instead of having span names
that contain all user ids.
Merge pull request #46 from joeslice/pattern-span-name

Allow client span names to be set based on pattern matching.
Update change log for 2.4-SNAPSHOT.
Correct project description.
resteasy3 integration. using deprecated PreProcessor but working
Update trace and span id conversion from Long to String.

When sending trace and span ids over the wire Zipkin hex encodes
the id's in case http is used. There was an earlier fix for Brave
which made the hex encoding compatible with Zipkin / Finagle but this
fix was not complete. Negative span and trace id's were not compatible.
This commit fixes this.

This is important in case you want to mix brave services with finagle
zipkin services.
Merge pull request #49 from kristofa/fix-negative-trace-ids

Fix negative trace ids
Update changelog for 2.4-SNAPSHOT.
Merge remote-tracking branch 'upstream/master' into resteasy3-integration
merged implementations of resteasy and jersey to jaxrs2. added some tests. removed code from -resteasy3 and -jersey2. only thing left in respective modules is corresponding integration test
test fix
added filter configuration for resteasy3-spring
unused imports fix and redundand dependency removed
Merge pull request #48 from tinedel/resteasy3-integration

Added resteasy3 integration using JAX-RS2 and reworked jersey2 implementation to also use JAX-RS2 support.
Update change log for 2.4-SNAPSHOT.
[maven-release-plugin] prepare release brave-2.4
[maven-release-plugin] prepare for next development iteration
Update change log.

Indicate version 2.4 is released.