Plugin not longer working after Kotlin 1.1.2 update.

[ethauvin]

All the Kobalt projects that I have updated to Kotlin 1.1.2, per IDEA's popup recommendation, are no longer functional.

They get into the following loop over and over:

I've tried selecting as Kotlin (Kobalt) module but that just throws an error.

[ethauvin]

Fix didn't help. The only difference I could see is that now I can select as Kotlin (Kobalt) module, which does stop the loop behavior, but now it is not resolving dependencies:

[ethauvin]

Any progress on this? Still can't use the plugin while it's looping like that.

[cbeust]

For what it's worth, everything seems to be working for me (both on MacOS and Windows).

@dmitry-zhuravlev, any idea what's going on with Eriks' configuration?

[ethauvin]

To be sure I created a new project:

kobaltw --init kotlin

And imported it into IDEA:

[dmitry-zhuravlev]

@ethauvin I think the problem here that you choose not proper Kotlin lib configurator.
The proper one is as Kotlin (Kobalt) module. The rest configurators have no idea about Kobalt project and cannot adjust the Build.kt in corresponding way.

Also there was a dissucussion with @cbeust about sending Kotlin libs directly to plugin when refresh button pressed: #79 (comment)
In case if we implement such behaviour the Configure Kotlin tooltip will be not needed anymore.
But this is not work yet....

[cbeust]

@dmitry-zhuravlev But until this is done automatically, just specifying kotlin-stdlib and kotlin-runtime in your dependencies should work as well, right?

[dmitry-zhuravlev]

just specifying kotlin-stdlib and kotlin-runtime in your dependencies should work as well, right?

Yep, this is what exactly what as Kotlin (Kobalt) module do. But also can be done manually simple by editing Build.kt dependencies section.

FYI just created some PR to Kotlin plugin: JetBrains/kotlin#1067
this will help to hide as Kotlin (Java) module and as Kotlin (JavaScript) module. It would be good if JB accept it and this will hide default configurators just to not confuse users.

[ethauvin]

@dmitry-zhuravlev As stated in #80 (comment), choosing as Kotlin (Kobalt) module does not work either. It does stop the looping but no longer finds Kobalt's own libraries.

[ethauvin]

Here it is in pictures:

Basically still unusable.

[dmitry-zhuravlev]

Hmm... But on the last screenshot I see that some classes from com.beust.* and com.google.* packages are not resolved. I guess that this should be from compileOnly("com.beust:$kobaltDependency:") dependency.
I tried to add compile("org.jetbrains.kotlin:kotlin-stdlib:1.1.2-2") in Build.kt and all classes from the standard Kotlin lib resolved fine.

@cbeust did Kobalt server even send compileOnly dependencies to plugin?
@ethauvin can you try to change from compileOnly to compile and press "Import changes" on tooltip?

[ethauvin]

Yes, that fixed the issue. Makes no sense, compileOnly was implemented weeks ago, and there weren't any issues until I updated the Kotlin runtime.

[ethauvin]

@cbeust can you make sure that compileOnly deps are sent to the plugin? I'd do it, but I know nothing about the server portion of kobalt.

[cbeust]

Will do but you can already quickly check yourself:

./kobaltw --server --force --log 2

Then push the Sync button in IDE, the server should give you the list of dependencies it's sending to the IDE.