-
Notifications
You must be signed in to change notification settings - Fork 41.3k
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
Use Brave BOM instead of only managing a single Zipkin dependency #32614
Conversation
8b178a8
to
b87d2b7
Compare
group("io.zipkin.reporter2") { | ||
modules = [ | ||
"zipkin-sender-urlconnection" | ||
library("Zipkin", "5.14.1") { |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brave sounds good!
Thanks, @marcingrzejszczak. |
Zipkin dependencies will come via Zipkin BOM