Interesting, TIL, I was surprised that the import even worked for resolving that extension at all. I always have thought you needed to bring

MyObject

into scope to actually use the extensions defined within it.

with(MyObject) {
  println("".myMethod())
}

@semoro there's another one like it here: https://youtrack.jetbrains.com/issue/KT-18416

Looks like the debugger does not show object properties?!

@orangy commented on @horse_badorties’s file : Please file a kotl.in/issue

@horse_badorties commented on @horse_badorties’s file : https://youtrack.jetbrains.com/issue/KT-19733

@User uploaded a file:

i tried looking through the issue-tracker, but i might have missed it (in that case, sorry) bug: when trying to move a

fun

from an

object

, move command (F6) does nothing. no dialog, no error message, just nothing

I think there is a bug with the code inspection tool

It gived me the "Unnecessary module dependency" I executed it and now my test folder can't reference the source one 😣

how can I revert it?

and this is not a Kotlin bug and should be reported in the IntelliJ issue tracker

Sorry Dmitry, I know that probably it's not the super correct channel to post it but I can't proceed working with the project (which indeed is in Kotlin so 😅 )

how do you update the maven runtime version? I get a warning in IJ about 1.1.3 even though plugin is 1.1.4 .. but when I build my project it says 1.1.4 for both runtime and stdlib in the build output. When I search my POMs I have only 1.1.4 as the defined property. Where else should I be looking?

@Dalinar do you mean kotlin runtime version? I had a dependency that included an old version, and got a similiar warning. I used the gradle task

dependencies

to find it. Not sure how maven does that

Hi! After upgrading to 1.1.4 we are experiencing a very weird behaviour. It appears that our test classes are not recognised anymore by IDEA (despite the source code being marked as test sources). The green play icon does not appear anymore. More importantly, some imports do not work, (in particular for fluentlenium, but we are not sure this is relevant). IDEA does not recognise these dependencies, although they are perfectly valid gradle dependencies (gradle works just fine in the command line). Also we seem to have lost all sort of IDE validation, IDEA won't complain anymore about syntactic errors or anything like that. We have spent quite a bit of time and can't figure out what's going on. Any hints? Thanks!

Not sure if my problem is with intellij 2017.2.2 or kotlin 1.1.4, but some dependencies fail to resolve. Eg.

kotlin.io.use

from

kotlin-stdlib-jre8

can't be found any more (and others, even my own modules (

compile project(':someModule')

) are failing).

@krissrex we also have deps failing to resolve

(fluentlenium)

We might have the same problem

valid import, existing dep, happy gradle, unhappy IDEA 😢

I've spent two days trying to solve it, with no success. The best bet seems to be a downgrade of versions (intellij, kotlin, gradle kotlin plugin)

we were considering that option, same code seems to work with kotlin plugin 1.1.3... Unfortunately there is no panic button in the plugin management panel

I assume you guys tried the obvious things like a clean build, clearing Idea's caches and reimporting the project?

@karelpeeters that has been our entire day

It was worth a shot ☺️

And very much appreciated ❤️

@karelpeeters I've not tried reimporting

I tried to use both

source sets as modules

and not; no difference. I tried using both

java

and

java-library

plugins, with

compile

and

implementation

. I tried adding stuff to compile with

scopes.COMPILE.plus += [ configurations.compile]

when they were `provided`+`runtime` (happens when you disable module per source set). Nothing I do seems to work

@User uploaded a file: