jamesfredley commented on issue #15896:
URL: https://github.com/apache/grails-core/issues/15896#issuecomment-5947363719
Confirmed on `8.0.x` at `d13aa332`.
`./gradlew runCommand` printed `Application class not found` when
`spring-boot-devtools` was on the classpath.
`GrailsApplicationContextCommandRunner.main` loads the application class with
the thread context classloader, and DevTools'' restart classloader made that
lookup fail. Commenters on this issue already showed that removing
`developmentOnly("org.springframework.boot:spring-boot-devtools")` lets the
same command get past this error.
That restart classloader is now turned off for the forked `runCommand` and
`runScript` JVMs with `spring.devtools.restart.enabled=false`. The change is
`dfb684d376` (2025-07-17), "Resolve conflicts between Spring Boot Dev Tools and
Gradle runCommand and runScript tasks". On this branch it is in
`grails-gradle/plugins/src/main/groovy/org/grails/gradle/plugin/commands/GrailsCliGradlePlugin.groovy`.
The commit is in `v7.0.0-RC1` and the later 7.0, 7.1, and 7.2 tags except
`v7.0.16`, and in `v8.0.0-M1` through `v8.0.0-RC2`.
The later `grails-app/conf/spring/resources.groovy` message is a missing
file for `s2-quickstart`, which is separate from this lookup.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
