This message was deleted.

dbm-xxx still works. However you might need to put profile back to your build.gradle as a work around

Hrm, I'm using grails 6.1.0 and just trying to run

grails dbm-gorm-diff test.groovy

it's showing me this error: ❯ grails dbm-gorm-diff test.groovy Unmatched arguments from index 0: 'dbm-gorm-diff', 'test.groovy'

6.1.0? That's something I did not try, my version is 6.0.0. And as you mentioned, they can work as gradle task as well. The attachment is from one of my current 6.0.0 project

Ah, so the profile only enables running them as gradle tasks. Makes sense, my tasks are working since we have the profile defined. It looks like you worked around the grails command support by calling the gradle tasks directly?

Yes. anything I got frustrated by grails command line, I go directly to gradle tasks. but I do agree with you, they need to keep the dev command stable and it can be very frustrated some time.

So the head line here is the plugins that added gradle scripts don't work anymore so you either have to add an intellij shortcut or an alias to now use them? @puneetbehl is this the official recommendation? That means the grails dbm-gorm-diff test.groovy now becomes ./gradlew runCommand "-Pargs=dbmGormDiff test.groovy"

Yes, you would have to run them via Gradle tasks.