you can do a

outputs.upToDateWhen { false }

on whatever task you are trying to disable the up-to-date checking on

ah, got it, thanks. is it possible to control that per test? or just for all tasks as a whole? i guess i could try and break this test into it's own task somehow

the one i posted only gives you task level granularity, you will have to do some additional logic if you are trying to break it down further - another task could be a good approach

Is there any eta on when gradle script kotlin will be released? This year? Q1 next year? How close is it to being finished?

Is http://repo.gradle.org/gradle/dist-snapshots/ supposed to be down right now? I can't find any information about it.

@bamboo What work needs to be done to get the Model Based DLS to work in Kotlin? Is there a plan to support it? Has there been some thought into how it will work? Will it require a significant amount of work to get the API to work correctly and for it to be consumable?

@jlleitschuh I doubt it will be supported, software model is officially deprecated

Hmm maybe I interpreted it differently https://docs.gradle.org/4.2/release-notes.html

We are deprecating Gradle's RuleSource and implementing native support in the current model.

And from the blog post - https://blog.gradle.org/state-and-future-of-the-gradle-software-model

The rule engine that was part of the Software Model will be deprecated

So maybe my interpretation is wrong

Is there a

gradle

task that will launch in the console the

kotlinc

REPL with the project classpath ready?

That's been fixed. https://github.com/gradle/kotlin-dsl/issues/512

I still try to figure out, how to use “kotlinVersion” defined in gradle.properties for kotlin() within a plugins {} block

@hastebrot uploaded a file: Untitled

@hastebrot You can’t use variables in a plugins block, only literal strings

Not being able to use variables in the plugins block is a major bug. 🐛 Is there an open issue for this?

it’s how plugins block works in Gradle

Since this PR, that hasn’t really been necessary - just specify the plugin version, the libraries will get it through a resolution strategy https://github.com/JetBrains/kotlin/pull/775

Or, https://github.com/nebula-plugins/nebula-kotlin-plugin/ which does a bit more

Thanks for the links and comments people, very helpful 😄

Hmm, the PR is from 2015. Does it use

embeddedKotlinVersion

? I think I recently saw some changes to this code.

No, embeddedKotlinVersion is kotlin-dsl feature and applied only when you use

kotlin()

shortcut for dependencies

You can check this discussion and upcoming changes of

embeddedKotlinVersion

https://github.com/gradle/kotlin-dsl/issues/465

@hastebrot https://github.com/gradle/gradle/issues/1697 is open for that , and i found a sort of hacky workaround in newer versions of Gradle that have

pluginManagement

in the

settings.gradle

at https://discuss.gradle.org/t/settings-gradle-not-finding-properties-from-gradle-properties/18175/14?u=mkobit

that is in addition to what the others have said about how

embeddedKotlinVersion

is changing and how the kotlin gradle plugin supports omitting dependency versions

Using Android Studio 3 Beta 7 by the way

Are there docs on the DSL grammar? Are all the verbs provided by the core DSL described? I see the examples, they're helpful until I reach an uncovered situation.

@camdenorrb uploaded a file:

Ugh, I'm confused

Please ping me if you know the issue

Simply can't get it to find that import, even when the import is placed manually