[ 
https://issues.apache.org/jira/browse/GROOVY-11428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommy Svensson closed GROOVY-11428.
-----------------------------------
    Resolution: Invalid

Me stubborn and tired! Groovys complaint is valid!

> WARNING: An illegal reflective access operation has occurred
> ------------------------------------------------------------
>
>                 Key: GROOVY-11428
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11428
>             Project: Groovy
>          Issue Type: Bug
>         Environment: Mac OS X Version 17.5 (19618.2.12.11.6)
>            Reporter: Tommy Svensson
>            Priority: Critical
>
> Now I have debugged over and over and over to finally find this:
>                Map<String, Object> map = [:]
>               ...
>                 LinkedHashMap<String, Object> resMap = new LinkedHashMap()
>                 resMap.putAll( map ) <=== This is the one producing:
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v9.Java9 
> (file:/Users/tommy/.m2/repository/org/apache/groovy/groovy/4.0.21/groovy-4.0.21.jar)
>  to field java.lang.reflect.Proxy.h
> WARNING: Please consider reporting this to the maintainers of 
> org.codehaus.groovy.vmplugin.v9.Java9
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> This seems like very legal code to me! 
> I can also add that when single-stepping through the code in debugger (IDEA) 
> the above does not occur! No warning displayed!
> This makes me believe that the problem occur if run to fast! Since there is a 
> Groovy specific plugin involved here I'd say this is a Groovy problem!
> I can also add that I'm working on an Apple M1 Pro (I think Apple call it). 
> 64 GB memory and 10 core processor. It is really fast! I believe that this is 
> relevant due to working fine when run slower in debug mode.
> I do consider this a Groovy issue! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to