https://kotlinlang.org logo
Channels
Powered by
#eap
  • i

    ilya.gorbunov

    01/17/2017, 8:04 PM
    That's unfortunate, seems no way to get these settings set up, other than reimporting gradle project
  • h

    hackerham

    01/17/2017, 8:09 PM
    😞
  • h

    hackerham

    01/17/2017, 8:09 PM
    300+ warnings every time i reload gradle
  • d

    damian

    01/17/2017, 8:11 PM
    Strange. I've deleted 
    .idea
    and 
    .gradle*
    and re-opened with no effect... can't imagine what else I'd need to do. In AS you can just open the gradle project.
  • d

    damian

    01/17/2017, 8:11 PM
    But I did see this: 
    Cannot add jps/kotlin-jps-plugin.jar from plugin 'Kotlin' to external compiler classpath: home directory of plugin not found
  • d

    damian

    01/17/2017, 8:11 PM
    could be nothing though
  • i

    ilya.gorbunov

    01/17/2017, 8:14 PM
    @damian In 
    app.iml
    file there should be the section 
    <facet type="kotlin-language" name="Kotlin">
    and 
    <KotlinVersionInfo>
    inside it. Could you check that?
  • d

    damian

    01/17/2017, 8:23 PM
    ahha @ilya.gorbunov
    Copy code
    <KotlinVersionInfo>
            <option name="apiLevel" value="1.0" />
            <option name="languageLevel" value="1.0" />
            <option name="targetPlatformName" value="JVM 1.6" />
          </KotlinVersionInfo>
  • i

    ilya.gorbunov

    01/17/2017, 8:24 PM
    So that's why there are warnings in IDE. Change these versions (apiLevel, languageLevel) to 1.1.
  • d

    damian

    01/17/2017, 8:25 PM
    er well actually I will have to do that in a few minutes. I forgot I had since given up and switched to a 1.0.6 branch. I will look again and try that once I finish this up
  • d

    damian

    01/17/2017, 8:25 PM
    thanks for your help 🙂
  • i

    ilya.gorbunov

    01/17/2017, 8:26 PM
    These versions should be inferred automatically from kotlin gradle plugin version and kotlin-stdlib version, specified in build.gradle, but for some reason it didn't happen
  • a

    alex2069

    01/17/2017, 10:36 PM
    @ilya.gorbunov I just got this as well. I was trying to test kapt issues I was having using 1.1; so uninstalled 1.1, installed 1.0.6 (not EAP), tested stuff, then put 1.1 back in. Multiple parts of code in another project kept giving "This feature is only available since Kotlin 1.1". Fixed it as above (changed "apiLevel" and "languageLevel" to "1.1"). Is it worth creating an issue for this since it will be moot when 1.1 is released anyway?
  • d

    damian

    01/17/2017, 11:14 PM
    Yeah, fwiw I came back to the problem and changing the versions in 
    KotlinVersionInfo
    fixed the problem. Not sure what prevented it from being updated.
  • s

    sdeleuze

    01/17/2017, 11:16 PM
    I have tried to upgrade my Mixit application to 
    1.1.0-beta-17
    / 
    1.1.0-dev-6111
    , but I have the following issues :
  • s

    sdeleuze

    01/17/2017, 11:17 PM
    1) In the IDE (I updated the IDEA plugin to 
    1.1.0-dev-6111
    ), 
    Exception
    can’t be resolved at this line https://github.com/sdeleuze/mixit/blob/kotlin-1.1/build.gradle.kts#L76
  • s

    sdeleuze

    01/17/2017, 11:18 PM
    2) When I run 
    ./gradlew clean test
    , I get the following error
  • s

    sdeleuze

    01/17/2017, 11:19 PM
    Copy code
    janv. 18, 2017 12:18:06 AM org.junit.platform.launcher.core.ServiceLoaderTestEngineRegistry loadTestEngines
INFOS: Discovered TestEngines with IDs: [spek]
java.lang.IllegalStateException: Resource not found in classpath: kotlin/coroutines/intrinsics/intrinsics.kotlin_builtins
        at kotlin.reflect.jvm.internal.impl.builtins.BuiltInsPackageFragmentProviderKt.createBuiltInPackageFragmentProvider(builtInsPackageFragmentProvider.kt:39)
        at kotlin.reflect.jvm.internal.impl.builtins.KotlinBuiltIns.createBuiltInsModule(KotlinBuiltIns.java:146)
  • s

    sdeleuze

    01/17/2017, 11:20 PM
    These errors can be reproduced with the 
    kotlin-1.1
    branch of my project https://github.com/sdeleuze/mixit/tree/kotlin-1.1
  • s

    sdeleuze

    01/17/2017, 11:21 PM
    And are regressions since this was working with 
    1.1-M04
  • s

    sdeleuze

    01/17/2017, 11:22 PM
    Any chance you can fix these in order to allow me to validate https://youtrack.jetbrains.com/issue/KT-15686 fix ?
  • i

    ilya.gorbunov

    01/18/2017, 12:04 AM
    @alex2069 It could be already fixed in the coming next milestone, but it's better to file an issue nevertheless, so we won't forget to ensure that it really is so.
  • u

    udalov

    01/18/2017, 8:35 AM
    @sdeleuze This is fixed now in 1.1.0-dev-6158 (available in kotlin-dev on Bintray) and will be fixed in 1.1-beta shortly
  • s

    sdeleuze

    01/18/2017, 8:35 AM
    Awesome thanks!
  • u

    udalov

    01/18/2017, 9:50 AM
    Also, 1.1-beta-17 has been republished to kotlin-dev on Bintray. If you happened to use its previous incarnation and want to try the new one, you should remove it from Gradle/Maven caches
  • u

    udalov

    01/18/2017, 9:51 AM
    although it should be pretty much identical to 1.1.0-dev-6158
  • k

    kirillrakhman

    01/19/2017, 12:52 PM
    Will 1.0.7 come out before 1.1? It would be weird if it was the other way round.
  • n

    nhaarman

    01/19/2017, 1:23 PM
    Why?
  • k

    kirillrakhman

    01/19/2017, 2:53 PM
    (I hope) the situation with kotlin is not like python 2 & 3 where both will coexist indefinitely. As I understand it, once kotlin 1.1 is released, there's no point in having 1.0.X releases
    👍 3
  • n

    neworldlt

    01/19/2017, 3:00 PM
    I hope 1.0.7 will be released ASAP. Life is to short for non-incremental builds (2-3 min each)
1...505152...106Latest