fernando88to opened a new pull request, #424:
URL: https://github.com/apache/grails-intellij-plugin/pull/424
## Problem
Grails 8 projects (Gradle 9) were not recognized as Grails projects: no run
configuration, no "New Grails Controller", and `Ctrl+Alt+G` did nothing.
On Grails 6
the run configuration was never created automatically either.
## Cause
- The Gradle model builder called `implementation.copy(...)`, which Gradle
9 rejects,
so the model build failed and the module was not tagged as Grails.
- A shell that could not be resolved also made the model build fail. For
example,
`grails-shell` was never published for 6.2.0 (#396).
- Code inherited from the JetBrains plugin disabled Grails run
configurations for
every version from Grails 6 on.
## Changes
- Resolve the shell through a detached configuration, and read
`grailsVersion` with
`findProperty()`. When the property is missing, take the version from
`grails-core`.
- If the shell cannot be resolved, keep the module as a Grails module.
Only the command
executor becomes unavailable.
- Offer Grails run configurations for Grails 6+ whenever the shell was
resolved.
## Tests
New Gradle import tests for Grails 8.0.0-M6 (Gradle 9.6) and Grails
6.2.3/6.2.0
(Gradle 7.6), with and without a resolvable shell. Checked manually in the
IDE with
Grails 8 and Grails 6 projects. The 3 failures in the full suite also fail
on `main`:
Gradle 4.6 needs JDK 8, and `GspResourceTagTest` is affected by test
pollution.
Fixes #396
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
