IntelliJ Gradle Support: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
There are cases when Gradle pulls the latest version of the SNAPSHOT and caches it in its [[Gradle_Dependencies_and_Dependency_Configurations#The_Dependency_Cache|dependency cache]], but IntelliJ IDEA Gradle plugin does not seem to notice it and uses an old version of the snapshot. This is troublesome during debugging, when the source code as displayed by IntelliJ does not match the bytecode being debugged. | There are cases when Gradle pulls the latest version of the SNAPSHOT and caches it in its [[Gradle_Dependencies_and_Dependency_Configurations#The_Dependency_Cache|dependency cache]], but IntelliJ IDEA Gradle plugin does not seem to notice it and uses an old version of the snapshot. This is troublesome during debugging, when the source code as displayed by IntelliJ does not match the bytecode being debugged. | ||
Possible solutions for this: | Possible solutions for this <font color=darkgray>(have not tested any of them, do that next time when I need it)</font>: | ||
====1. Refresh Dependencies==== | |||
Revision as of 21:10, 9 October 2018
External
Internal
Overview
If asked to specify Gradle home, and get "Gradle location is incorrect", use the "libexec" subdirectory (/usr/local/Cellar/gradle/4.9/libexec).
Importing a Project form a Gradle Model
Use auto-import - If selected, re-import of the project is done automatically every time you make changes to the project.
Group modules. See Grouping Modules.
SNAPSHOT Refresh Problem
There are cases when Gradle pulls the latest version of the SNAPSHOT and caches it in its dependency cache, but IntelliJ IDEA Gradle plugin does not seem to notice it and uses an old version of the snapshot. This is troublesome during debugging, when the source code as displayed by IntelliJ does not match the bytecode being debugged.
Possible solutions for this (have not tested any of them, do that next time when I need it):