Grails debugging broken by maven in 15.*

Using IntelliJ 15, the debugger won't stop at breakpoints if Grails is configured to get the dependencies using a pom.xml file and if the pom.xml added to the "Maven Projects" window.

Using Grails 2.4.3, and various official and EAP builds of IntelliJ 15.
This issue started with the support of Grails3.

There might be a combination of grails-maven-plugin settings to fix it but I haven't found it yet.

Steps (or download the attached app and skip to 6.)
1. Create a Grails 2.4.3 app
2. Create a dummy controller and put a breakpoint
3. From the command line run "grails create-pom com.example"
4. Change BuildConfig to
```
grails.project.dependency.resolution = {
pom true
...
dependencies {
}

plugins {
}
```
5. Run the app in debug mode and navigate to the controller
==> IntelliJ stops at the breakpoint
6. Add pom.xml to the "Maven Projects" window.
7. Restart the app in debug mode and navigate to the controller
==> IntelliJ **does not stop** at the breakpoint.

Having the pom.xml file as a Maven project is important because that's how IntelliJ synchronizes its project settings with the pom file.

---

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

Reproduce the six steps with Grails 2.4.3, IntelliJ 15, BuildConfig using pom dependencies, and pom.xml imported in the Maven Projects window. Compare debugging before and after Maven import, focusing on the Grails debug configuration and Maven project synchronization. Done means the controller breakpoint is reached after restarting the app in debug mode with pom.xml registered.

Written by the indexing model from the issue text.