apache / apache/grails-intellij-plugin
Grails user library doesn't recognize Maven modules in same project
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
Steps to reproduce:
1. Create a new project.
2. Create a Maven module with some Java class in it, and install it in the local repository.
3. Create a Grails module that references the Maven module as a dependency.
4. Write some Groovy code that uses a class in the Maven module.
5. In the Groovy code, try "go to definition" on the class from the Maven module.
Expected:
- IDEA navigates to the source code in the Maven module.
Actual:
- IDEA navigates to the compiled JAR in ~/.grails/ivy-cache
---
*Imported from [IDEA-89023](https://youtrack.jetbrains.com/issue/IDEA-89023) · Type: Bug · Votes: 1*
*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 Maven-module and Grails-module setup, then start at the dependency resolution and “go to definition” behavior described in the issue. Trace why navigation selects the compiled JAR in ~/.grails/ivy-cache instead of the Maven module source; done means the class reference navigates to that source code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100