This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 219307 - It is not possible to remove Grails project after removing Grails
Summary: It is not possible to remove Grails project after removing Grails
Status: NEW
Alias: None
Product: groovy
Classification: Unclassified
Component: Grails (show other bugs)
Version: 7.3
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-02 07:12 UTC by michal.owsiak
Modified: 2012-10-22 15:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Message when removing grails with non existing Grails installation (21.38 KB, image/png)
2012-10-02 07:12 UTC, michal.owsiak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description michal.owsiak 2012-10-02 07:12:55 UTC
Created attachment 125189 [details]
Message when removing grails with non existing Grails installation

Use-case:

1. Configure Grails environment in NetBeans
2. Create Grails project in NetBeans
3. Remove Grails installation
4. Try to remove project from NetBeans

This issue may severely affect people who just want to try out the Grails in NetBeans.
Comment 1 Martin Janicek 2012-10-02 08:21:38 UTC
Thanks for the report. I'll take a look at it
Comment 2 Martin Janicek 2012-10-02 08:47:21 UTC
Mm, I've tried to reproduce with no success.
I tried this:

1. Configured NetBeans
2. Create Grails project
3. Using "apt-get remove" uninstall Grails
4. Trying to close Grails project with no problem at all

Can you see any differences between your steps and mine? And what do you see if you go into the Tools/Options/Miscellaneous/Groovy? I still see the path to the old installation of Grails, which is obviously wrong, but another issue. It could be the reason why you got the error message and I don't.
Comment 3 Martin Janicek 2012-10-22 15:14:59 UTC
I'm decreasing the priority to P3. I can't reproduce the scenario described in comment 1, but I believe it's possible to get the Options dialog to an inconsistent state somehow which would probably result in such warning.
I'll try to make the UI a little bit safer to avoid those issues.