The GitHub Actions job "CI" on grails-intellij-plugin.git/main has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: b40209a6da1d63bd30dd9d19c73908b7f7ec0d46 / James Daugherty <[email protected]> Report an unresolvable Grails shell in the Build tool window and tag the new importing tests - findResolvedVersion returned null whenever compileClasspath existed (an inverted null check left over from debugging), so the grails-core fallback never ran and a project without a grailsVersion property lost its Grails support. - The model builder now extends AbstractModelBuilderService so that a shell it cannot resolve is reported through the ModelBuilderContext message reporter as a Build tool window warning, naming the coordinates and the repository to add, instead of a line in the Gradle log only. The Grails 8 import test asserts the message in the sync view. - GradleApacheGrailsImportingTest and GradleGrails6ImportingTest carry @Category(UltimateOnlyTest.class) like GradleGrailsImportingTest, so the Community Edition test task keeps skipping the importers built on the Gradle test framework. - The Grails 8 import test pins 8.0.0-RC1 on Gradle 9.7.1, the Gradle its shell depends on, and leaves out the grails-gsp plugin: the RC1 GroovyPagePlugin trips a Gradle 10 deprecation under the "fail" warning mode the importing tests run with. Report URL: https://github.com/apache/grails-intellij-plugin/actions/runs/36819928403 With regards, GitHub Actions via GitBox
