apache / apache/grails-intellij-plugin

Grails 3 - Dependencies not re-index when added to build.gradle after initial import

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

Reproduce:
Import new Grails 3.0.10, import as Gradle (Import from existing -> double click build.gradle). Using gradle wrapper and Auto import is set to false (if it's true grails imports/traits do not work)

Let IDEA resolve/index deps. Intellisense works.

Add 1 new dependency to build.gradle, eg `compile 'com.sendgrid:sendgrid-java:2.2.2'`

IDEA indexes, but that dependency is not resolved in intellisense. Any sendgrid imports/object are red.

Work around -
Blow away the IDEA project and re-import the project, leaving the dependency in build.gradle. After the initial index that dependency that wasn't available to intellisense is now working.

---

*Imported from [IDEA-149513](https://youtrack.jetbrains.com/issue/IDEA-149513) · 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 problem with the Grails 3.0.10 project and its build.gradle, using the Gradle wrapper with Auto import disabled. Compare dependency indexing after adding sendgrid-java with indexing after a full project re-import. Done means the added dependency resolves in IntelliJ intellisense without deleting and re-importing the project.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, devtools
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.