Skip to content

Use Brave BOM instead of only managing a single Zipkin dependency #32614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

marcingrzejszczak
Copy link
Contributor

@marcingrzejszczak marcingrzejszczak commented Oct 6, 2022

Zipkin dependencies will come via Zipkin BOM

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 6, 2022
@marcingrzejszczak marcingrzejszczak changed the title Adds all Observability related BOMs Use Zipkin BOM instead of managing a Zipkin dependency Oct 6, 2022
group("io.zipkin.reporter2") {
modules = [
"zipkin-sender-urlconnection"
library("Zipkin", "5.14.1") {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should rename this. Perhaps "Zipkin Brave" or just "Brave". What would you recommend?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenZipkin Brave would be most correct I guess (https://github.com/openzipkin/brave).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They don't seem to use "Open Zipkin" anywhere really though. The README for https://github.com/openzipkin/brave just talks about "Brave" and "Zipkin". The bom describes itself as "Bill Of Materials POM for all Brave artifacts". I'm leaning towards "Brave".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brave sounds good!

@wilkinsona wilkinsona added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 6, 2022
@wilkinsona wilkinsona added this to the 3.0.x milestone Oct 6, 2022
@wilkinsona wilkinsona added the for: merge-with-amendments Needs some changes when we merge label Oct 6, 2022
@wilkinsona wilkinsona changed the title Use Zipkin BOM instead of managing a Zipkin dependency Use Brave BOM instead of only managing a single Zipkin dependency Oct 6, 2022
@wilkinsona wilkinsona modified the milestones: 3.0.x, 3.0.0-RC1 Oct 6, 2022
@wilkinsona wilkinsona closed this in 99a0109 Oct 6, 2022
@wilkinsona
Copy link
Member

Thanks, @marcingrzejszczak.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: merge-with-amendments Needs some changes when we merge type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants