kotlinlang #gradle

Trying out the Kotlin DSL. In the Groovy DSL, I have jacocoTestReport { reports { xml.enabled true } } I haven't been able to figure out how to achieve the same in the Kotlin DSL.

mhurne

07/13/2017, 8:11 PM

My Gradle fundamentals are pretty weak, so that's not helping

mhurne

07/13/2017, 8:16 PM

I'm thinking it belongs in the tasks { } block

jlleitschuh

07/13/2017, 8:27 PM

That may work.

jlleitschuh

07/13/2017, 8:29 PM

Run

./gradlew gskProjAccessors

and gradle will print out some helpful code you can copy into your build so that the

jacocoTestReport

symbol resolves itself.

mhurne

07/13/2017, 8:57 PM

Interesting, thanks. Doesn't seem to pull in the JacocoReportsContainer ?

user

07/13/2017, 9:49 PM

0.10.3 Gradle Kotlin DSL 0.10.3 Release Notes Gradle Kotlin DSL v0.10.3 is meant to fix a defect in the artifacts published as part of the v0.10.2 release which are otherwise identical. Please refer to the v0.10.1 and v0.10.2 release notes for details on what's included. v0.10.3 is...

🌮 1

elect

07/14/2017, 1:47 PM

@elect has left the channel

dagguh

07/14/2017, 7:08 PM

My build works from CLI perfectly, but IDEA complains. Refreshes, deleting cache, reimporting the project don’t help.

user

07/14/2017, 7:13 PM

@dagguh commented on @dagguh’s file

https://kotlinlang.slack.com/files/U4K74R58Q/F692K9V0T/idea-cant-see-wrapper.png▾

: Any IDEAs how to make IDEA see it’s all good? 🙂

galex

07/17/2017, 11:10 AM

I mean that if you have a library as a separate project, this feature lets you work on it locally without having to deploy a new version to your local or distant maven repository and upgrade versions every 5 minutes.

dragas

07/17/2017, 11:16 AM

@galex: Did you try

compile project(":moduleName")

galex

07/17/2017, 11:19 AM

@dragas I mean more than that, lets say you have your dependency to a library like this: compile ‘com.examplelib1.0.0’ but you’re working on this lib right now in a separate project, on every change you would have to release at least to your local maven repo a new .jar with a new version number

galex

07/17/2017, 11:20 AM

I read a way to configure in your gradle.properties that this artifact can be indicated to come from another project (not module) locally on your machine

dragas

07/17/2017, 11:21 AM

Meanwhile, is it possible to mark multiple flavor folders as source folders, without each of them claiming that class is being redeclared? Every time gradle syncs my project, additional (not main) source folders get unmarked, thus preventing intellij from indexing that flavor.

dragas

07/17/2017, 11:21 AM

Copy code

include ":logger"
project(":logger").projectDir = file("../logger")

dragas

07/17/2017, 11:21 AM

As seen on https://stackoverflow.com/questions/19299316/require-gradle-project-from-another-directory?noredirect=1

mkobit

07/17/2017, 3:51 PM

@galex https://docs.gradle.org/current/userguide/composite_builds.html

mkobit

07/17/2017, 3:51 PM

I think that's what you are looking for

trevjones

07/17/2017, 4:09 PM

composite builds would be ideal if they work for the situation but if you are using anything but a trivial java build they tend to not work. example. being android.

trevjones

07/17/2017, 4:10 PM

in that case you can create a method in your

settings.gradle

file. something like

Copy code

def maybeIncludeProject(projectName, projectPath) {
     if (file(projectPath).exists()) {
        println "Including project '$projectName' @ '$projectPath'"
        include projectName
        project(projectName).projectDir = file(projectPath)
    } else {
        println "Project '$projectName' was not found @ '$projectPath'. Skipping inclusion."
    }
}

trevjones

07/17/2017, 4:11 PM

then in your root

build.gradle

add something like

Copy code

boolean hasProject(projectName) {
    try {
        project(projectName)
        return true
    } catch (error) {
        return false
    }
}

def projectElseArtifact(projectName, artifactPath) {
    if (hasProject(projectName)) {
        return project(projectName)
    } else {
        return artifactPath
    }
}

trevjones

07/17/2017, 4:12 PM

so your dependency declaration becomes something like

compile projectElseArtifact(':foo', 'com.example:foo:1.0.0')

trevjones

07/17/2017, 4:13 PM

again a typical dependency substitution policy would be better but those tend to fail due to android. so if you can safely use them I would say do it rather than the

projectElseArtifact

and use the

hasProject

to determine if you should perform said substitution

galex

07/18/2017, 2:45 AM

@mkobit Thank you!!

gaetan

07/18/2017, 4:28 PM

Sorry to bother you guys but I need some indications on where should I start. It’s very hard to find information. There are few versions of gradle. Which one should we use? Some jetbrain’s projects use 2.x versions (https://github.com/JetBrains/kotlin-web-demo/blob/master/gradle/wrapper/gradle-wrapper.properties). Kotlin is using 3.2 (https://github.com/JetBrains/kotlin/blob/master/gradle/wrapper/gradle-wrapper.properties). The current version of gradle is 4.0.1. kotlinlang has a link on it. It should be stable enought, so why the kotlin project does not use it?

07/18/2017, 4:31 PM

use the latest stable version

agomez

07/18/2017, 4:31 PM

my guess is because it's not that easy to upgrade dependencies in big projects

agomez

07/18/2017, 4:32 PM

i'm using 4.0.1 in my actual kotlin project and works fine

harmony

07/18/2017, 7:12 PM

is it possible to exclude files from compilation? I replace something in my build.gradle and set the new sources in

compileKotlin

but it complains about redeclarations

Copy code

compileKotlin {
  dependsOn sourceMainKotlin
  source = file('build/sources/kotlin')
}