You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently upgrading an application from Grails 6 to Grails 7 which uses the grails-quartz plugin.
When I created a new Grails 7.2.2 project with the Quartz plugin included, I was not able to start it with ./gradlew bootRun. The error output can be seen here: grails-quartz-starter-issue-error.txt
The command I used to create the project is the following:
grails-forge-cli create-app --servlet=tomcat --jdk=17 --gorm=hibernate --reloading=devtools --features=grails-quartz app
# same result with since the build.gradle is only minimally different
grails -t forge create-app --servlet=tomcat --jdk=17 --gorm=hibernate --reloading=devtools --features=grails-quartz com.grintec.web4sw.swebserver
After prompting an LLM multiple times I found that from 3.0.x -> 4.0.x the dependency org.springframework:spring-context-support was removed.
When I added the above dependency explicitly, I was able to start the application.
Would it be possible to add the dependency back to build.gradle or put some kind of information into the documentation that this package is needed? (I am not sure how the (transitive) dependencies / BOM etc. are handled in Grails 7.x.x)
@TheCrether This was missed and ideally would be in an upgrade guide or the feature would automatically add it. I've raised a concern on the mailing list and suggested we migrate this repo into the grails-core repo like we have other changes so these type of maintenance steps are easier.
Activity
jdaugherty commentedon Aug 13, 2026
@TheCrether This was missed and ideally would be in an upgrade guide or the feature would automatically add it. I've raised a concern on the mailing list and suggested we migrate this repo into the grails-core repo like we have other changes so these type of maintenance steps are easier.
jdaugherty commentedon Aug 23, 2026
As part of the merge to grails-core, this will be corrected in the next release.
TheCrether commentedon Aug 29, 2026
Thank you!