Use unsafe to inject classes to boot loader #4026
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ClassInjector.UsingInstrumentation
packages new classes in a temporary jar and callsInstrumentation.appendToBootstrapClassLoaderSearch
. This seems a bit excessive for just defining a few classes. IfUnsafe
is available then use it instead. I kept the original code as fallback, though this might not be necessary as withjvmArgs("-Dnet.bytebuddy.safe=true")
which disables unsafe tests fail withI believe there is a good chance that this resolves #3896