-
Notifications
You must be signed in to change notification settings - Fork 11
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 Byte Buddy for Instrumentation by default #389
Conversation
Previous behavior can be used by setting the `instrument.dynamic-proxy` property to `true`.
Generate changelog in
|
Is it worth getting Java12/13 tests running on our OSS repos too? |
I fully support testing everything we possibly can. I've manually verified that the relevant tests to this change pass on java 12. |
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.
LGTM, defer to @schlosna to pull the trigger though!
Going to defer to @carterkozak when he's comfortable marking to "merge when ready" given ApacheCon this week |
I have comms, let's ship it. |
Previous behavior can be used by setting the
instrument.dynamic-proxy
property totrue
.Before this PR
Dynamic proxies were used by default.
After this PR
==COMMIT_MSG==
Use Byte Buddy for Instrumentation by default, reducing excess stack frames from instrumentation.
==COMMIT_MSG==
Possible downsides?
There's always a risk in change, particularly for environments with complex class loader hierarchies and security managers. We've rolled this out to our largest project already without any issues.