Skip to content
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

Merged
merged 3 commits into from
Sep 9, 2019

Conversation

carterkozak
Copy link
Contributor

Previous behavior can be used by setting the
instrument.dynamic-proxy property to true.

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.

Previous behavior can be used by setting the
`instrument.dynamic-proxy` property to `true`.
@changelog-app
Copy link

changelog-app bot commented Sep 6, 2019

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Use Byte Buddy for Instrumentation by default, reducing excess stack frames from instrumentation.

Check the box to generate changelog(s)

  • Generate changelog entry

@iamdanfox
Copy link
Contributor

Is it worth getting Java12/13 tests running on our OSS repos too?

@carterkozak
Copy link
Contributor Author

I fully support testing everything we possibly can. I've manually verified that the relevant tests to this change pass on java 12.

Copy link
Contributor

@iamdanfox iamdanfox left a 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!

@schlosna
Copy link
Contributor

schlosna commented Sep 9, 2019

Going to defer to @carterkozak when he's comfortable marking to "merge when ready" given ApacheCon this week

@carterkozak
Copy link
Contributor Author

I have comms, let's ship it.

@bulldozer-bot bulldozer-bot bot merged commit 124f7b5 into develop Sep 9, 2019
@bulldozer-bot bulldozer-bot bot deleted the ckozak/byte_buddy_default branch September 9, 2019 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants