Details
-
Wish
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
The new $getLookup() method was discussed somewhat in the comments of GROOVY-10273. Groovy 3 has had JEP 396 (illegal access enforcement) support backported to the invoke dynamic pathways, without $getLookup. So, I'd like to restart the discussion to find out if there are any illegal-access scenarios that Groovy 4 supports that don't have a test case in Groovy 3. And if there are no scenarios that remain, I'd like to propose the removal of $getLookup method generation.
I have disabled its generation in the Groovy 5 codebase, and there are no tests that fail. So I have good confidence that it can be removed and the security hole can be plugged.
Attachments
Issue Links
- is related to
-
GROOVY-10145 Support JDK16
- Closed
-
GROOVY-10290 Dynamic Groovy code in Gradle doesn't compile because of $getLookup() method is not static
- Closed
-
GROOVY-10319 Groovy3 CompileStatic bug: Method clone is protected in java.lang.Object
- Closed
-
GROOVY-10391 Default interface methods causing problems with java 17 and groovy 3.0.9
- Closed
-
GROOVY-10450 Cannot call BiPredicate methods on closures or lambdas on JRE 16+
- Closed
-
GROOVY-10709 Performance regression in Gradle with Groovy 4
- Closed
-
GROOVY-10273 New $getLookup() method is not marked as generated or internal
- Closed
-
GROOVY-9081 CLONE - Fix warning "An illegal reflective access operation has occurred"
- Closed
-
GROOVY-9103 CLONE - CLONE - Fix warning "An illegal reflective access operation has occurred"
- Closed
-
GROOVY-9144 Fix warning "An illegal reflective access operation has occurred"
- Closed
-
GROOVY-9217 Fix warning "An illegal reflective access operation has occurred" when setting property
- Closed
-
GROOVY-10438 DGM: getMetaPropertyValues and getProperties includes private entries
- Closed