Do you have a small sample of Groovy code which when compiled triggers the warning?
This is the kind of error we might expect when code is bending the rules for field access. It might be one of the cases we have fixed when running on later JDKs. It isn't necessarily a problem - it works fine when running on JDK11 and might go away when you eventually upgrade. You might be able to hush the warning with compiler switches. Cheers, Paul. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Jun 1, 2024 at 8:10 PM Tommy Svensson <to...@natusoft.se> wrote: > > Hello Groovers, > > I keep getting this when building: > > 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 > > I've tried both GraalVM and Bellsofts JDK 11 build. Both report the same. > > I do need to stay at 11 right now! > > Regards, > > Tommy Svensson > > to...@natusoft.se > > >
