Grails 7.0.0-M1 - Grails Run Command fails from IntelliJ

[jamesfredley]

Issue description

./grailsw does work

But Grails Run Command fails from IntelliJ does not.

Error: Unable to initialize main class org.grails.cli.GrailsCli
Caused by: java.lang.NoClassDefFoundError: org/gradle/tooling/BuildCancelledException

[jamesfredley]

#13919 solved this for the grails distribution.

[jamesfredley]

#13958 requires org.gradle:gradle-tooling-api which Gradle only publishes to https://repo.gradle.org/gradle/libs-releases/ and not to mavenCentral(). This has been a recurring issue that we have worked on a few times on grails-core for grails-shell CLI. Most recently this was solved for the grails distribution on https://github.com/grails/grails-core/pull/13919/files

1. If we expose the org.gradle:gradle-tooling-api dependency, as would be the normal path, we end up having to add the https://repo.gradle.org/gradle/libs-releases/ repository to many projects and the end Grails application. We decided not to do this and changed the dependency to compileOnly a few months back. Unfortunately it keeps popping up. We need to revisit this decision about adding the extra repository or follow one of the following two alternative paths.

2. In researching it today, I found that netbeans ran into this issue also and has published a mirrored version of gradle-tooling-api to mavenCentral() for about 5 years. https://central.sonatype.com/artifact/org.netbeans.external/gradle-tooling-api/overview . netbeans does publish it slightly less frequently.

https://mvnrepository.com/artifact/org.netbeans.external/gradle-tooling-api vs https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api?repo=gradle-libs-releases

What are your thoughts on using this dependency instead?

3. Another potential solution would be a virtual repository on repo.grails.org to pull it in from https://repo.gradle.org/gradle/libs-releases/.