-
Notifications
You must be signed in to change notification settings - Fork 124
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
Fix "Class path contains multiple SLF4J bindings" during runtime atta… #380
Conversation
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.
maybe runtime-attach-distro
-> runtime-attach-core
since typically I think of -distro
as depending on the underlying component, and so it is a little strange to see runtime-attach
depend on runtime-attach-distro
runtime-attach-distro/src/main/java/io/opentelemetry/contrib/attach/AgentFileProvider.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Trask Stalnaker <[email protected]>
Changes done |
runtime-attach-core/src/main/java/io/opentelemetry/contrib/attach/AgentFileProvider.java
Show resolved
Hide resolved
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.
thx!
I have just realized that it may be possible to simplify the implementation with the uber jar (the temporary folder might become unecessary). Please let me check before continuing the review. |
My idea to simplify the implementation does not work. Please continue the review. |
thx! |
This PR fixes a "Class path contains multiple SLF4J bindings" warning during runtime attachment.
The agent jar file is no longer added to the classpath. Now, it is included in the runtime attach artifact.
A project dedicated to providers of the OpenTelemetry Java agent is added. It can help them to build a dependency to runtime attach their agent jar file.