apache / apache/grails-intellij-plugin

GrailsCompileStatic now results in error warnings for mapping closure.

Open
#340 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

After upgrading to the newest bug fix release, I find that the table as well as version lines on Grails 3.x domain classes trigger an IDE "error" line if the class is marked with @GrailsCompileStatic. These classes were previously not flagged in the previous IntelliJ version and the commandline / gradle compiles fine. While this isn't a fatal error, it's pretty annoying to open up code and see an bunch of error flags.

IU-183.4588.61, JRE 1.8.0_152-release-1343-b16x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080, 1920x1080

---

*Imported from [IDEA-203988](https://youtrack.jetbrains.com/issue/IDEA-203988) · Type: Bug · Votes: 2*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no repository files, tests, or entry points. Reproduce the IDE warning on a Grails 3.x domain class using @GrailsCompileStatic with table and version mappings, then identify the affected inspection and verify that valid mappings no longer receive error markers while command-line and Gradle compilation still succeed.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.