https://kotlinlang.org logo
Channels
Powered by
#spring
  • s

    sdeleuze

    01/18/2018, 9:02 AM
    I am currently writing Kotlin Boot documentation that will specify that
  • s

    sdeleuze

    01/18/2018, 9:03 AM
    Does that make sense for you?
  • l

    lex

    01/18/2018, 9:13 AM
    @sdeleuze I mean that current 2.0.0.M7 bom contains 1.1.61 version of kotlin and it is affect to implicit dependencies, does it will be upgraded to 1.2.20? my build.gradle.kts:
    Copy code
    ...
buildscript {
    repositories {
        maven("<https://repo.spring.io/milestone>")
    }

    dependencies {
        classpath("org.springframework.boot:spring-boot-gradle-plugin:2.0.0.M7")
    }
}

apply {
    plugin("org.springframework.boot")
}

plugins {
    val kotlinVersion = "1.2.20"
    kotlin("jvm") version kotlinVersion
    kotlin("plugin.spring") version kotlinVersion
    kotlin("plugin.jpa") version kotlinVersion
    id("io.spring.dependency-management") version "1.0.4.RELEASE"
}
...
repositories {
    mavenCentral()
    jcenter()
    maven("<https://repo.spring.io/milestone>")
}

dependencies {
    compile(kotlin("stdlib-jdk8"))
    compile(kotlin("stdlib"))
    compile(kotlin("stdlib-jre7"))
    compile(kotlin("stdlib-jre8"))
    compile(kotlin("reflect"))
...
}
    without explicit declaration
    Copy code
    compile(kotlin("stdlib"))
compile(kotlin("stdlib-jre7"))
    it will be at 1.1.61 version
  • s

    sdeleuze

    01/18/2018, 9:17 AM
    With such Gradle config I think the inconsistency comes from the fact that you define Kotlin version at Kotlin plugin level, not Boot managed dependencies, hence my proposal to define it at buildscript.ext level. Notice that we currently do not manage 
    kotlin-stdlib-jdk7
    and 
    kotlin-stdlib-jdk8
    versions but that will be the case for RC1.
  • l

    lex

    01/18/2018, 9:21 AM
    yes, you are right. how I can define property on buildscript.ext level?
  • l

    lex

    01/18/2018, 9:22 AM
    I try this
    Copy code
    buildscript {
    ext {
        val kotlinVersion = "1.2.20"
    }
    repositories {
        maven("<https://repo.spring.io/milestone>")
    }

    dependencies {
        classpath("org.springframework.boot:spring-boot-gradle-plugin:2.0.0.M7")
    }
}

apply {
    plugin("org.springframework.boot")
}

plugins {
    kotlin("jvm")// version kotlinVersion
    kotlin("plugin.spring")// version kotlinVersion
    kotlin("plugin.jpa")// version kotlinVersion
    id("io.spring.dependency-management") version "1.0.4.RELEASE"
}
  • l

    lex

    01/18/2018, 9:22 AM
    but there error 
    build.gradle.kts:9:5: Unresolved reference: ext
  • l

    lex

    01/18/2018, 9:23 AM
    what is strange - idea does not show error
  • s

    sdeleuze

    01/18/2018, 9:23 AM
  • s

    sdeleuze

    01/18/2018, 9:24 AM
    Maybe with:
  • l

    lex

    01/18/2018, 9:24 AM
    I have a gsk script
  • l

    lex

    01/18/2018, 9:24 AM
    🙂
  • s

    sdeleuze

    01/18/2018, 9:25 AM
    Could you set the version of the Kotlin plugins explicitly ?
  • s

    sdeleuze

    01/18/2018, 9:25 AM
    Uncommenting // version
  • l

    lex

    01/18/2018, 9:27 AM
    yes, but kotlinVersion should be defined at plugins block, as first version
  • l

    lex

    01/18/2018, 9:28 AM
    @lex uploaded a file:

    image.png▾

  • s

    sdeleuze

    01/18/2018, 9:28 AM
    OK I am going to have a look on one of my projects
  • s

    sdeleuze

    01/18/2018, 10:47 AM
    For now, i can only propose :
  • s

    sdeleuze

    01/18/2018, 10:47 AM
    Copy code
    plugins {
    val kotlinVersion = "1.2.20"
    id("org.jetbrains.kotlin.jvm") version kotlinVersion
    id("org.jetbrains.kotlin.plugin.spring") version kotlinVersion
    id("org.springframework.boot") version "2.0.0.M7"
    id("io.spring.dependency-management") version "1.0.4.RELEASE"
}

extra["kotlin.version"] = plugins.getPlugin(KotlinPluginWrapper::class.java).kotlinPluginVersion
  • s

    sdeleuze

    01/18/2018, 10:48 AM
    I am discussing with #gradle guys to provide a better solution in the future
  • l

    lex

    01/18/2018, 10:50 AM
    yes, that works, I saw it
  • l

    lex

    01/18/2018, 10:50 AM
    🙂
  • l

    lex

    01/18/2018, 10:51 AM
    I am at #gradle channel too
    👍 1
  • c

    Czar

    01/18/2018, 11:24 AM
    By the way, it's a bit unfortunate that spring plugin management has Kotlin version in a property 
    kotlin.version
    . This does not allow us to use 
    val kotlinVersion by extra
    syntax in the 
    build.gradle.kts
    we have to always use 
    extra["kotlin.version"]
    instead 😞
  • d

    dharrigan

    01/18/2018, 11:29 AM
    We do this in our build.gradle.kts file
  • f

    fabricio

    01/20/2018, 4:37 PM
    I have a weird behavior here with Spring Boot MongoDb. This document:
    Copy code
    @Document(collection = "schedules")
data class ScheduleDocument(val payload: Payload) {
}
    is stored as:
    Copy code
    {
    "_id" : ObjectId("5a636f2e5017622fc0c4654a"),
    "_class" : "example.Payload",
    "channel" : "push",
    "schedule" : ISODate("2018-01-20T16:32:46.535Z")
}
    But I was expecting 
    payload
    to be a subdocument, like this:
    Copy code
    {
	"_id" : ObjectId("5a636f2e5017622fc0c4654a"),
	"_class" : "example.ScheduleDocument",
	"payload": {
	    "channel" : "push",
	    "schedule" : ISODate("2018-01-20T16:32:46.535Z")
	}
}
    can anyone explain this behavior?
  • s

    sdeleuze

    01/22/2018, 8:53 AM
  • z

    ziggy42

    01/22/2018, 5:09 PM
    Am I the only one without sql syntax highlighting in 
    @Query
    annotations when using Kotlin?
  • z

    ziggy42

    01/22/2018, 5:13 PM
  • c

    Czar

    01/22/2018, 5:51 PM
1...139140141...173Latest