Bump cxf.zipkin-reporter.version from 2.17.2 to 3.1.1

[dependabot]

Bumps cxf.zipkin-reporter.version from 2.17.2 to 3.1.1.
Updates io.zipkin.reporter2:zipkin-reporter-brave from 2.17.2 to 3.1.1

Release notes

Sourced from io.zipkin.reporter2:zipkin-reporter-brave's releases.

Zipkin Reporter 3.1 adds custom encoding (non-JSON) support for zipkin-reporter-brave's AsyncZipkinSpanHandler.

This was first used in encoder-stackdriver-brave) to allow traced apps to send spans to stackdriver without a zipkin core jar dependency

spanHandler = AsyncZipkinSpanHandler.newBuilder(sender).build(new StackdriverV2Encoder(Tags.ERROR));

Full Changelog: openzipkin/zipkin-reporter-java@3.0.1...3.1.1

Zipkin Reporter 3.0.1 fixes a problem where classpath scanners such as spring would trigger a zipkin2.Span class load on AsyncZipkinSpanHandler in zipkin-reporter-brave, which intentionally has no dependency on that.

Zipkin Reporter 3.0.0 makes the io.zipkin.zipkin2:zipkin dependency of io.zipkin.reporter2:zipkin-reporter-brave optional. This means those using the AsyncZipkinSpanHandler will have no dependencies except any sender they configure. In particular, this allows those using Brave for things besides zipkin (e.g. wavefront) to avoid a dependency. Also, those sending spans zipkin have simpler dependency configuration and save a couple hundred KB, as well.

Those using types from the core io.zipkin.reporter2:zipkin-reporter artifact should depend on this directly, possibly using our bom to align deps. io.zipkin.reporter2:zipkin-reporter still defaults to depend on io.zipkin.zipkin2:zipkin, but it can be excluded if you know what you are doing.

Technically, some base classes to accommodate this, but they don't have affect on call sites except those implementing a custom Reporter or Sender. Due to these type changes, this is a major version change. However, must users will have a drop-in experience, except possibly dependency configuration changes.

Thanks a lot to @​anuraaga and @​reta who helped think through this!

Commits

• 9508452 [maven-release-plugin] prepare release 3.1.1
• 9c666c4 ci: deploys bom separately to allow re-do on partial failure (#241)
• 73ac34b Increases deploy timeouts due to recent failures uploading to sonatype (#240)
• 4c57453 [maven-release-plugin] prepare for next development iteration
• 36a160d [maven-release-plugin] prepare release 3.1.0
• dea1650 brave: allows AsyncZipkinSpanHandler to be built with custom formats (#239)
• af70e4c [maven-release-plugin] prepare for next development iteration
• 4587e0e [maven-release-plugin] prepare release 3.0.2
• 3f9229d [maven-release-plugin] prepare for next development iteration
• a21e3e4 [maven-release-plugin] prepare release 3.0.1
• Additional commits viewable in compare view

Updates io.zipkin.reporter2:zipkin-sender-urlconnection from 2.17.2 to 3.1.1

Release notes

Sourced from io.zipkin.reporter2:zipkin-sender-urlconnection's releases.

Zipkin Reporter 3.1 adds custom encoding (non-JSON) support for zipkin-reporter-brave's AsyncZipkinSpanHandler.

This was first used in encoder-stackdriver-brave) to allow traced apps to send spans to stackdriver without a zipkin core jar dependency

spanHandler = AsyncZipkinSpanHandler.newBuilder(sender).build(new StackdriverV2Encoder(Tags.ERROR));

Full Changelog: openzipkin/zipkin-reporter-java@3.0.1...3.1.1

Zipkin Reporter 3.0.1 fixes a problem where classpath scanners such as spring would trigger a zipkin2.Span class load on AsyncZipkinSpanHandler in zipkin-reporter-brave, which intentionally has no dependency on that.

Zipkin Reporter 3.0.0 makes the io.zipkin.zipkin2:zipkin dependency of io.zipkin.reporter2:zipkin-reporter-brave optional. This means those using the AsyncZipkinSpanHandler will have no dependencies except any sender they configure. In particular, this allows those using Brave for things besides zipkin (e.g. wavefront) to avoid a dependency. Also, those sending spans zipkin have simpler dependency configuration and save a couple hundred KB, as well.

Those using types from the core io.zipkin.reporter2:zipkin-reporter artifact should depend on this directly, possibly using our bom to align deps. io.zipkin.reporter2:zipkin-reporter still defaults to depend on io.zipkin.zipkin2:zipkin, but it can be excluded if you know what you are doing.

Technically, some base classes to accommodate this, but they don't have affect on call sites except those implementing a custom Reporter or Sender. Due to these type changes, this is a major version change. However, must users will have a drop-in experience, except possibly dependency configuration changes.

Thanks a lot to @​anuraaga and @​reta who helped think through this!

Commits

• 9508452 [maven-release-plugin] prepare release 3.1.1
• 9c666c4 ci: deploys bom separately to allow re-do on partial failure (#241)
• 73ac34b Increases deploy timeouts due to recent failures uploading to sonatype (#240)
• 4c57453 [maven-release-plugin] prepare for next development iteration
• 36a160d [maven-release-plugin] prepare release 3.1.0
• dea1650 brave: allows AsyncZipkinSpanHandler to be built with custom formats (#239)
• af70e4c [maven-release-plugin] prepare for next development iteration
• 4587e0e [maven-release-plugin] prepare release 3.0.2
• 3f9229d [maven-release-plugin] prepare for next development iteration
• a21e3e4 [maven-release-plugin] prepare release 3.0.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[reta]

Closing, will be addressed in https://issues.apache.org/jira/browse/CXF-8969

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.