Gradle v1.12 fails to refresh projects using IntelliJ

Old Forum
1

When I try to refresh the configuration using “Refresh all Gradle projects” button in IntelliJ I get the following error:

Gradle 'projectname' project refresh failed:
Cause: org.gradle.plugins.ide.internal.IdeDependenciesExtractor.extractRepoFileDependencies(Lorg/gradle/api/artifacts/ConfigurationContainer;Ljava/util/Collection;Ljava/util/Collection;ZZ)Ljava/util/List;

Everything seems to work fine when I change the version back to Gradle v1.11

The version of IntelliJ is: IntelliJ IDEA 13.1.2 Build #IU-135.690, built on April 17, 2014

I remember there was a similar problem with Gradle v1.11 in previous version on IntelliJ and it seems that the new version haven’t resolved it completely.

2

Can you try their EAP build 135.760 from http://confluence.jetbrains.com/display/IDEADEV/IDEA+13.1+EAP ?

Related bug report says it’s fixed in 13.1.3 and that’s what is currently available as EAP only.

3

Just tried the EAP and can confirm that indeed it works perfectly fine under IU-135.760

Looks like the choice is to either use EAP and v1.12 or simply hold back from upgrading gradle until the next release. Actually, the same scenario as with Gradle v1.11 prior to IntelliJ 13.1

4

Issue also exists in Android studio 0.5.7

5

What is the release date of 13.1.3?

6

13.1.3 was released yesterday:

http://blog.jetbrains.com/idea/2014/05/intellij-idea-13-1-3-update-is-available/

7

13.1.3 has a new issue with the Gradle integration: http://youtrack.jetbrains.com/issue/IDEA-125592

8

Here’s the error I’m receiving:

Gradle 'geb' project refresh failed:
 // Can't register given path of type 'SOURCE' because it's out of content root.
 // Content root: .../geb/buildSrc'
 // Given path: ...\geb\integration\geb-gradle\src\main\groovy': Gradle settings (a minute ago)

IntelliJ 13.1.3 Community Edition, Gradle 1.10

9

Todd, this thread is related to Gradle 1.12 interaction with IntelliJ. Should we create a new one for your problem? And add more complete description to it because it is really hard to deduce what is the problem from your post.

10

Sorry, I just assumed this issue was similar to the one I’m facing.

11

oks like the choice is to either use EAP and v1.12 or simply hold back from upgrading gradle until the next release. Actually, the same scenario

70-417

12

oks like the choice is to either use EAP and v1.12 or simply hold back from upgrading gradle until the next release. Actually, the same scenario as wi

http://www.spanishprograms.com

13

And add more complete description to it because it is really hard to deduce what is the problem from your post.???