apache / apache/grails-intellij-plugin

Grails 3.2 log implicit property is assumed to be commons logging instead of slf4j

Open
#311 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

The Grails plugin seems to assume the implicit log property added to all Grails 3.2.x artefacts are Commons Logging objects, however, in Grails 3.2.x the log objects were [changed to slf4j](http://docs.grails.org/latest/guide/upgrading.html#_slf4j_now_default). This means that using a log method like `log.debug('Test {}', 'test')` compiles and runs without error but gets marked as an error in the IDE and autocompletion options are all from commons logging.

Steps to reproduce:
1. `sdk use grails 3.2.11`
2. `grails create-app test`
3. Create any grails artefact, eg a controller
4. Import test project into IDE
5. Attempt to use autocomplete on implicit log property in artefact

---

*Imported from [IDEA-176469](https://youtrack.jetbrains.com/issue/IDEA-176469) · Type: Bug · Votes: 8*
*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

Reproduce the problem with Grails 3.2.11 by creating an application and artefact, then importing it into IntelliJ IDEA. Start by tracing how the plugin types the implicit log property and compare that with Grails 3.2.x's SLF4J default; it is done when SLF4J methods and autocomplete are recognized without an IDE error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.