Scott Murphy

I diagnosed my issue and found it is do to having multiple `dataSources` configured in `application.yml` [Example App](https://github.com/codeconsole/grails4bugs) I have created the following issue that needs to be resolved in...

This will probably depend on Groovy 4.x support https://github.com/grails/grails-core/issues/12373

I can confirm Grails 5.1.7 working with JDK 17 using Groovy 3.0.11-SNAPSHOT I had to use `gradle bootRun` However, the grails cli does not work. ``` % grails | Error...

The only JDK 17 issues that seem to be remaining are grails cli issues. ``` % grails -v | Grails Version: 5.1.8 | JVM Version: 17.0.3 % grails create-app grails4bugs...

FYI JDK 17 is version 61 so the CLI is not supporting compiling itself

This seems like an issue being enforced by the framework https://github.com/grails/grails-spring-security-core/issues/767 https://github.com/grails-plugins/grails-spring-security-ui/issues/127 https://github.com/grails/grails-spring-security-core/issues/737

I've encountered the same issue upgrading a Grails app from 5.1.1 to 5.1.7 with a drain class that contains `@GrailsCompileStatic(TypeCheckingMode.SKIP)` I can confirm switching to `@CompileDynamic` resolves the issue.

@sagrawal31 just switch `@GrailsCompileStatic(TypeCheckingMode.SKIP)` to `@CompileDynamic`

I think all the plugins can be handled by adding an exclude in build.grade that prevents the groovy 3 jar from resolving

Well, the org.codehaus.* packages still exist https://docs.groovy-lang.org/latest/html/gapi/index.html Perhaps if there are plugins that never upgraded the packages to groovy 3 would be an issue. **Legacy package removal** https://groovy-lang.org/releasenotes/groovy-4.0.html A decision...