conflict on capability 'org.codehaus.groovy:groovy:3.0.24' also provided by org.apache.groovy:groovy:4.0.26

[jamesfredley]

Issue description

The following conflict is now occurring on grails-shell and grails-forge generated 7.0.0-SNAPSHOT applications

A problem occurred configuring root project 'Test22'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.apache.groovy:groovy:4.0.26.
     Required by:
         root project : > org.apache.grails:grails-bom:7.0.0-SNAPSHOT:20250517.183431-81 > org.apache.groovy:groovy-bom:4.0.26
         root project : > org.apache.grails:grails-bom:7.0.0-SNAPSHOT:20250517.183431-81 > org.apache.grails:grails-spring:7.0.0-SNAPSHOT:20250517.183431-81 > org.apache.groovy:groovy-xml:4.0.26
      > Module 'org.apache.groovy:groovy' has been rejected:
           Cannot select module with conflict on capability 'org.codehaus.groovy:groovy:4.0.26' also provided by [org.codehaus.groovy:groovy:3.0.24(runtime)]
   > Could not resolve org.codehaus.groovy:groovy.
     Required by:
         root project : > org.apache.grails:grails-gradle-plugins:7.0.0-SNAPSHOT:20250517.180618-108
      > Module 'org.codehaus.groovy:groovy' has been rejected:
           Cannot select module with conflict on capability 'org.codehaus.groovy:groovy:3.0.24' also provided by [org.apache.groovy:groovy:4.0.26(groovyRuntimeElements)]
> There are 2 more failures with identical causes.

[jamesfredley]

It is this commit: 2840260

[jdaugherty]

Gradle tasks are isolated which means it doesn't have access to the version of groovy that gradle has - so we have to provide it. Otherwise, when the FindMainTask calls the MainClassFinder it will fail saying groovy was not found. Gradle plugins, however, are not isolated. In my testing, this still worked when we provided it.

I didn't see a conflict when testing locally. This error some how indicates the gradle classpath is getting onto the application classpath?

[jdaugherty]

Per original PR discussion, we had debated if we needed a separate project. Given that people are still including grails projects with commands in the gradle import, this problem can occur.

We backed out my change on exposing groovy and instead moved the task to a separate gradle project where we could expose groovy only to the tasks.