spring-boot-devtools conflict with gradlew runCommand

[hellobigbean]

No qualifying bean of type 'grails.plugins.GrailsPluginManager' available

Expected Behavior

grails 6.1.2, 6.2.0 and 7.0.0-SNAPSHOT

gradlew runCommand -Pargs="generate-controller sampleapp.ClassA" --scan
report: https://scans.gradle.com/s/e7wqodd3gnxmk

Actual Behaviour

No response

Steps To Reproduce

No response

Environment Information

No response

Example Application

No response

Version

6.1.2, 6.2.0 and 7.0.0-SNAPSHOT

[matrei]

Hi @hellobigbean,

I haven’t been able to replicate the error on my end. Could you share the project or more details about it?
It would help me investigate further.

Thanks!

[codeconsole]

@matrei the issue occurs when you add spring-boot-devtools to your build.gradle

dependencies {
    // ...
    developmentOnly("org.springframework.boot:spring-boot-devtools")
}

@hellobigbean do you have that dependency? if so, try commenting out temporarily then running the command.

[jamesfredley]

I can confirm that with developmentOnly("org.springframework.boot:spring-boot-devtools") this error occurs on a Grails 6.2.0 project and without it does not occur.

[jamesfredley]

https://github.com/grails/grails-core/blob/c0ac9667e5d55db544cd62155ad17f8322ca1b25/grails-console/src/main/groovy/grails/ui/command/GrailsApplicationContextCommandRunner.groovy#L43-L59

https://github.com/grails/grails-core/blob/c0ac9667e5d55db544cd62155ad17f8322ca1b25/grails-core/src/main/groovy/grails/boot/GrailsApp.groovy#L97-L113

[puneetbehl]

I think this might be happening due to some dependency might be missing from the restart classloader. We've faced serveral issues in the past due to JARs or classes while using "spring-boot-devtools". I'll try to look into this and share more details soon.

[puneetbehl]

Also, it seems similar to #13509