Bugfix/groovy 9541 respect parent classloader #1814
Closed
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.
Helpful background may be found in the comments of https://issues.apache.org/jira/browse/GROOVY-9541.
As @eric-milles noted there, we may need to do a more careful consideration of each consumer of
StaticTypeCheckingSupport#evaluateExpression, since thesourceobject's classloader may not actually be correct in every case.I can attest that letting
org.codehaus.groovy.transform.ASTTransformationCollectorCodeVisitor#findCollectedAnnotationsuse the context classloader will result in difficult-to-resolve cases of GROOVY-9541.A word about 4616fc8: without that, you'll get a cast_failure when trying to compile the groovy-macro module. I was a bit nervous about it, but I think
java.util.Optional#mapprovides enough null safety that it should work.My local test suite is still finishing execution, but I thought a concrete diff & a PR would be helpful for the discussion.