apache / apache/grails-intellij-plugin

Grails console stops responding, can't run any commands

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

I’ve recently started having issues with the Grails plugin for IntelliJ where running a console command that generates an error will cause the command console to ‘lock up’. My only recourse is to quit the IDE. The kill process button doesn’t do anything either. Here’s a screenshot:

_⚠️ attachment `image.png` was not included in the export_{width=70%}
```
Apple Macbook M1 Pro running ventura
IntelliJ 2023.1.1 Ultimate edition
Grails Plugin 231.8770.17
```
I just upgraded to this latest version today to see if it resolved my issue but it did not. Previously I had been running a 2022 environment and had the same issue

## To reproduce:

1. Use a Grails project but have something that may generate an error, e.g an incorrect maven dependency listed
2. Right click on project in Project Window
3. Select Grails -> Run Grails Command
4. Select clean-all and hit ok

The command runs and executes. It produces the error but then ‘locks up’ any further grails command usage. If I click ‘kill process’ I get ‘Process Terminated’ in red text in the console window but the process never terminates. Only solution I know is to restart. I’m going to work with the command line as work around but it would be nice to know if this could be fixed.

---

*1 attachment(s) referenced here (`image.png`) are not part of the CSV export.*
*Imported from [IDEA-319533](https://youtrack.jetbrains.com/issue/IDEA-319533) · Type: Bug · Votes: 5*
*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 lock-up in IntelliJ 2023.1.1 with the Grails plugin by running clean-all on a project with an incorrect Maven dependency. Start by tracing the plugin's Grails command console and process termination handling; done means the console accepts later commands and Kill Process actually terminates the failed process.

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.