apache / apache/grails-intellij-plugin

Grails 3 auto reloading of controllers not working

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

What steps will reproduce the issue?
1. Take any Grails 3.3 project
2. Start the project as a Java application
3. Change the controller class.

What is the expected result?
I see in the console log show:
File /path/to/controller/SomeController.groovy changed, recompiling...

However, hitting that controller does not result the new code executing.

What happens instead?
Old code keeps getting executed.

IntelliJ version being used:
IntelliJ IDEA 2017.3.4 (Ultimate Edition)
Build #IU-173.4548.28, built on January 29, 2018
Licensed to ``
You have a perpetual fallback license for this version
Subscription is active until January 8, 2019
JRE: 1.8.0_152-release-1024-b11 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.3

---

*Imported from [IDEA-186365](https://youtrack.jetbrains.com/issue/IDEA-186365) · Type: Bug · Votes: 0*
*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 issue with a Grails 3.3 project started as a Java application in IntelliJ IDEA, then change a controller and verify the reload log and request behavior. Trace the IntelliJ/Grails controller reload path from the reported recompilation event; done means changed controller code executes without restarting the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.