https://kotlinlang.org logo
Channels
Powered by
#gradle
  • b

    Bernhard

    02/21/2019, 9:44 AM
    Copy code
    tasks.withType<KotlinCompile> {
    kotlinOptions {
        jvmTarget = "1.8"
        freeCompilerArgs = listOf("-Xjsr305=strict")
    }
}
  • b

    Bernhard

    02/21/2019, 9:45 AM
    hm, ok, builds just fine in my terminal
  • b

    Bernhard

    02/21/2019, 9:46 AM
    IDE bug?
  • b

    Bernhard

    02/21/2019, 10:05 AM
    ah, apparently the facet wasn’t imported correctly
  • m

    mp

    02/22/2019, 4:08 AM
    Oddly, IntelliJ thinks the gradle build typechecks fine (no red)
  • b

    bjonnh

    02/25/2019, 8:48 PM
    and will gradlew handle that correctly ?
  • a

    alec

    03/02/2019, 8:15 PM
    Cross posting here in case someone knows:
  • m

    Marc Knaup

    03/04/2019, 4:55 AM
    1.2.3 also broken, for a different reason:
    Copy code
    org.gradle.kotlin.dsl.accessors.PluginAccessorsClassPathKt.writeSourceCodeForPluginSpecBuildersFor(Lorg/gradle/internal/classpath/ClassPath;Ljava/io/File;Ljava/lang/String;)V
    Many unstable releases in quite a short timeframe 😕
  • b

    Bernhard

    03/04/2019, 4:03 PM
    I have some unit tests in my buildSrc/ folder and I am somehow unable to load a file from buildSrc/src/test/resources/test.txt via get javaClass.getResource(“test.txt”) inside my test
  • b

    Bernhard

    03/04/2019, 4:03 PM
    I’m using intellij to run the tests btw
  • b

    Bernhard

    03/04/2019, 4:04 PM
    https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec%3abuild_sources also doesn’t mention a resources/ folder so is that supported at all?
  • h

    hmole

    03/05/2019, 4:34 PM
    Is there a way to disable 
    .module
    publishing for gradle 
    maven-publish
    publication? I a dependency in my mpp project on a plugin which uses shadow to shade it's dependencies, but when gradle tries to resolve it it starts to look for the shadowed dependencies since they are declared in plugins 
    .module
    file.
  • m

    mp

    03/05/2019, 6:08 PM
    CLI gradle has no problems
  • r

    rsetkus

    03/06/2019, 5:21 PM
    Hi! Have a question about for those who uses Detekt. This is how looks my root build.gradle script.
    Copy code
    apply from: 'dependencies.gradle'

buildscript {
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.2'
    }
}
    I cannot introduce 
    plugins {}
    block in the root gradle script and I cannot remove 
    apply from: 'dependencies.gradle'
    either because dependencies.gradle has to be executed before module build.gradle script Can anybody tell what other options are to set up Detekt? Many thanks in advance
  • n

    Nikky

    03/06/2019, 5:56 PM
    i think yo ucan move 
    apply from: 'dependencies.gradle'
    into the buildscript block, before repositories or into a buildSrc, and get rid of the buildscript block by configuring setting.gradle(.kts) properly (add google() and jcenter() to pluginRepositories)
    👍 1
  • c

    Czar

    03/06/2019, 6:06 PM
    I'd ask in #detekt , also if memory serves detekt has many examples in its docs and github.
    👍 1
  • t

    thomasnield

    03/06/2019, 9:18 PM
    When i've got a Kotlin multiproject setup, and I specify the plugin in the parent and child projects like so:
  • t

    thomasnield

    03/06/2019, 9:19 PM
    plugins { kotlin("jvm") version "1.3.21" }
  • o

    octylFractal

    03/06/2019, 9:20 PM
    putting it in `buildSrc`'s dependencies might be the best way
  • g

    gildor

    03/06/2019, 11:28 PM
  • g

    gildor

    03/07/2019, 12:29 AM
    2 cool Kotlin related things in this release: 1. Type-safe accessors in kotlin-dsl for pre compiled plugins, now it will be easier to extract some common configs and just create plugins, you can use the same syntax as in build.gradle.kts 2. Metadata 1.0, is a huge thing for Kotlin MPP publishing, hope all MPP plugins and libraries will migrate to metadata 1.0 and will be much more stable and not depending on particular versions of Gradle
    👌 1
    👍 6
    🎉 1
  • m

    mike_shysh

    03/12/2019, 3:53 PM
    HI to everyone! I wonder whether someone knows how gradle spawns 'Gradle Test Executor N' if "maxParrallelForks" is 1 (default). I run several jenkins tasks with "gradle test" and sometimes one jobs failes with ExitCode 143
    Copy code
    12:16:02.145 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED
12:16:02.145 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'Gradle Test Executor 2' finished with exit value 143 (state: FAILED)
12:16:02.146 [DEBUG] [org.gradle.internal.work.DefaultWorkerLeaseService] Worker lease root.1.35.100 completed (1 worker(s) in use)
12:16:02.146 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Dispatch org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor@201e8cf3: released lock on root.1.35.100
12:16:02.147 [DEBUG] [TestEventLogger]
  • m

    mike_shysh

    03/12/2019, 3:53 PM
    Gradle 5.1.1
  • m

    mike_shysh

    03/12/2019, 3:55 PM
    It's not a jenkins node overload case (as I thought earlier)
  • m

    mike_shysh

    03/12/2019, 3:57 PM
    I found out that build fails only when Gradle Test Executor 2 appears
  • b

    bjartek

    03/14/2019, 7:27 AM
    that is groovy code from an build.gradle file
  • t

    tapchicoma

    03/14/2019, 6:05 PM
    any reason that 
    InspectClassesForMultiModuleIC
    task (https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/tasks/InspectClassesForMultiModuleIC.kt) from kotlin plugin doesn't enable caching support? It is one of the tasks in my Gradle build scan that has "Not cacheable: Task output caching not enabled"
  • c

    cfleming

    03/18/2019, 1:54 AM
    I’ve put the following in my build script:
    Copy code
    println "Java version: ${JavaVersion.current()}, \$JAVA_HOME = ${System.properties['java.home']}"
    which results in:
    Copy code
    Java version: 1.8, $JAVA_HOME = /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
  • c

    cfleming

    03/18/2019, 1:55 AM
    I’ve also put:
    Copy code
    ext.javaHome = System.properties['java.home']
    in my 
    buildscript
    block, and then:
    Copy code
    compileKotlin {
  kotlinOptions {
    jdkHome = javaHome
    jvmTarget = "1.8"
  }
}
    but I still get the same error.
  • c

    cfleming

    03/18/2019, 1:57 AM
    Any ideas why that might be the case, or ideas for further diagnosis?
1...383384385...409Latest