Grails 7 grails-controller dependency

[bkoehm]

I have a plugin that I'm converting to Grails 7 which has a controller in it. I had to add org.apache.grails:grails-controllers as a dependency to my build.gradle to get my controller to work. @jdaugherty thinks perhaps that dependency should have been included already via one of the other dependencies I had. But it's entirely possible I just didn't have the right dependencies listed in the first place, so if that's the case, feel free to close this as a "not a bug",

Dependencies that I had listed where my controller didn't work:

    implementation "org.springframework.boot:spring-boot-starter-logging"
    implementation "org.apache.grails:grails-core"
    implementation "org.apache.grails:grails-web-boot"
    implementation "org.apache.grails:grails-cache"
    implementation "org.apache.grails:grails-converters"
    console "org.apache.grails:grails-console"
    profile "org.apache.grails.profiles:web-plugin"
    implementation "org.apache.grails:grails-services"

I added this and controller started working:

implementation "org.apache.grails:grails-controllers"

Using grails-core built at commit 9fef7c0 (May 2).

[jdaugherty]

I think the issue is the mix up of 'grails-web-url-mappings' and 'grails-url-mappings'. Forge isn't publishing yet (we're working on it, it's due to a GCP container registry transition).

When migrating, I'd suggest you use https://github.com/apache/grails-core/blob/7.0.x/etc/bin/rename_gradle_artifacts.sh to migrate your project versions. It will likely be faster.

Also, as a general rule, you should not have to import any group except 'org.apache.grails' for grails application dependencies. If you're importing 'org.apache.grails.web', then you're including a lower level library.