Updates to Brave 5.18 with zipkin-reporter 3

[codefromthecrypt]

No description provided.

[codefromthecrypt]

I think the failures are explainable and will go away in Brave 6, but @anuraaga @reta or @shakuzen if you can check my sanity. What this does is remove the zipkin dependency from zipkin-reporter, but brave still references zipkin core types. I think Spring autoconfig scans the whole file then would find those, and so the zipkin jar is needed for Spring autoconfig until Brave 6.

Ratpack, cassandra and dropwizard fail because they use third-party tracing which is not yet updated to avoid zipkin core types. Similar with sleuth (zipkin2.reporter.BytesMessageEncoder depends internally on zipkin types). These projects should claim their own dependency on zipkin-reporter (not incidentally through zipkin-reporter-brave) until they don't use those types. We can probably do that here and raise a PR on each accordingly. One reason to use zipkin-reporter is a project that uses formats besides json.

TL;DR; is I think zipkin-reporter 3 is good, as if it wasn't the other 5 tests wouldn't pass, so we can ship that an move forward to Brave (release 5.18 with reporter 3, but brave still has a zipkin dep for deprecateed methods.. then immediately Brave 6 to remove them)

[reta]

I think the failures are explainable and will go away in Brave 6, but @anuraaga @reta or @shakuzen if you can check my sanity.

I think it makes sense @codefromthecrypt , the 3.x is next major and it is fine to require some work for other projects to migrate (like those deps on zipkin you've mentioned).

[codefromthecrypt]

dropwizard-zipkin will be removed as the tracing repo was archived: #99

[codefromthecrypt]

removed ratpack as it was abandoned

[codefromthecrypt]

was at it, so updated cassandra

[codefromthecrypt]

sleuth uses an old version of zipkin-reporter and as it is unmaintained, probably won't update. Brave 6 removes version management from reporter for reasons like this.