-
-
Notifications
You must be signed in to change notification settings - Fork 953
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spring-boot-devtools conflict with gradlew runCommand #13523
Comments
Hi @hellobigbean, I haven’t been able to replicate the error on my end. Could you share the project or more details about it? Thanks! |
@matrei the issue occurs when you add dependencies {
// ...
developmentOnly("org.springframework.boot:spring-boot-devtools")
} @hellobigbean do you have that dependency? if so, try commenting out temporarily then running the command. |
I can confirm that with |
Lines 43 to 59 in c0ac966
grails-core/grails-core/src/main/groovy/grails/boot/GrailsApp.groovy Lines 97 to 113 in c0ac966
|
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. |
Also, it seems similar to #13509 |
No qualifying bean of type 'grails.plugins.GrailsPluginManager' available
Expected Behavior
grails 6.1.2, 6.2.0 and 7.0.0-SNAPSHOT
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
The text was updated successfully, but these errors were encountered: