IntelliJ IDEA using JavaScript "version" of dependency specified in Gradle build file?

Question

This issue just recently (past couple days) started occurring on one of my development machines.

I'm using Eclipse's Vert.x dependency for a web project:

build.gradle

dependencies {
    ...
    // Kotlin
    compile "org.jetbrains.kotlin:kotlin-stdlib-jre8:$kotlin_version"
    // Vert.x for web framework
    compile group: 'io.vertx', name: 'vertx-core', version: '3.4.2'
    compile group: 'io.vertx', name: 'vertx-web', version: '3.4.2'
    ...
}

This has worked fine in the past - I think the triggering action was my upgrading to IntelliJ 2017.2.2, but now:

IntelliJ cannot resolve any of the -web imports:

If I examine the Dependencies list for my Module, the JavaScript version of the dependency is shown?

How did this happen, and how can I make sure it's properly recognized as a Java dependency?

Edit: Sample project available here: https://youtrack.jetbrains.com/issue/IDEA-177950

Just a hunch, try moving your Kotlin apply plugin ... lines to below the dependencies, and/or Kotlin compile ... lines to the end within the dependencies, and full gradle resync. — Les
– Les, Commented Aug 23, 2017 at 12:12
Please report at youtrack.jetbrains.com/issues/IDEA with the Minimal, Complete, and Verifiable example attached. — CrazyCoder
– CrazyCoder, Commented Aug 23, 2017 at 12:30
Thanks @CrazyCoder, if I can reproduce in a smaller project I will be sure to do so. — Craig Otis
– Craig Otis, Commented Aug 23, 2017 at 12:31
@CrazyCoder issue opened, youtrack.jetbrains.com/issue/IDEA-177950. I've also updated this question with the same project for anyone interested in toying. — Craig Otis
– Craig Otis, Commented Aug 23, 2017 at 13:18

yole · Accepted Answer · 2017-08-23 13:22:02Z

3

This is a bug in the Kotlin plugin which is fixed in version 1.1.4-2. After you update the plugin, you need to delete the incorrect libraries and reimport your project from Gradle to have your project fixed.

answered Aug 23, 2017 at 13:22

yole

98k21 gold badges279 silver badges205 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Craig Otis Over a year ago

Indeed it is! As the JetBrains issue tracker is not publicly indexable, nothing came up in my searches. (And I searched less thoroughly through the tracker myself.) For reference, it is this issue: youtrack.jetbrains.com/issue/KT-19717

guenhter · Accepted Answer · 2017-08-23 11:01:01Z

0

If you face such problems, the first two things you always can do is:

(in IntellJ) File > Invalidate Caches/Restart
(in IntellJ's Gradle Bar) Press button for Refresh all gradle dependencies

If this doesn't help, please check if ./gradlew clean testClasses succeeds or also fails with such an error.

answered Aug 23, 2017 at 11:01

guenhter

12.3k5 gold badges40 silver badges71 bronze badges

2 Comments

Craig Otis Over a year ago

Thanks, I tried all both, to no avail. The CLI build is fine - the dependency resolution seems to be isolated to IntelliJ.

guenhter Over a year ago

Hm, that's really interesting. Just tried that out also with IntelliJ 2017.2.2 -> works perfectly fine. Can you provide your whole gradle file?

Collectives™ on Stack Overflow

IntelliJ IDEA using JavaScript "version" of dependency specified in Gradle build file?

2 Answers 2

1 Comment

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related