WELD-2744 CFW update and needed changes to keep operating correctly on JDK 17+ #2847
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.
CFW in version 1.3.0.Final includes following commit - jbossas/jboss-classfilewriter@4028c25
This means as soon as
DefaultClassFactory.INSTANCE
gets initialized, you need--add-opens
to be able to execute the code in there - else you're getting an exception.Even though we never use CFW to define classes, this still affects us because of the way we instantiate
ClassFile
in ourProxyFactory
- we use a deprecated method that now gets re-routed to a default implementation of the class factory.In order to bypass this, we need to use a variant of the
ClassFile
method where we specify CL as well asClassFactory
instance. This PR uses dummy variant to do just that.