Grails SDK not configured

It seems if I have multiple Grails projects open that have different versions of Grails, the IDE shows an alert saying that the Grails SDK is not configured for the project - but when I click the action link and configure a Grails SDK, the project then shows the same library included twice. It seems to be random on which project it does this for, but I think it's the project that wasn't last in focus.

I've seen the error stating that the Grails SDK is not configured many times in the past, but I'd just configure it and leave the IDE open for a long time and forget the problem. Recently I've been shutting down and restarting my machine more, and the problem has been more annoying.

Basically, I have 2 Grails projects which I have open in 2 different IDE windows. Project A is using Grails 2.3.5, and Project B is using Grails 2.4.0. It seems when I shut down the IDE and then restart it, one of the projects will start up and complain about the Grails SDK not being set. When I configure the SDK through the action-link, and then view the Module Settings, I see that the Grails Library is included multiple times (once extra for each time I see the error).

> Does this project have valid dependency on the Grails at this point (check in dependencies tab, or is there no dependency or is it broken? Does it happen only if one project is opened?

Yes it does have a valid dependency on Grails. The last screen shot I attached is the dependency view from the Module settings.

> Does it happen only if one project is opened?

No, it doesn't happen if I only have 1 project opened.

---

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

Reproduce the issue with two IDE windows containing Grails 2.3.5 and 2.4.0 projects, then use the Grails SDK action link and inspect Module Settings. Trace the SDK configuration and project-reopen flow, focusing on why the Grails Library is added repeatedly. Done means both projects retain their correct SDKs after restart without duplicate libraries.

Written by the indexing model from the issue text.