https://kotlinlang.org
Join Slack
Dumb question --- what’s the correct way to make a custom task that doesn’t take parameters? It see...
# gradle
p
Dumb question --- what’s the correct way to make a custom task that doesn’t take parameters? It seems like if I don’t specify any @Inputs, gradle complains that the constructor should be annotated with @Inject. If I annotate the task constructor with @Inject, gradle complains that the constructor doesn’t take any parameters.
https://stackoverflow.com/questions/65360274/custom-gradle-task-that-accesses-top-level-fails-with-the-constructor-shoul suggests that kotlin is quietly adding an implicit parameter, which is why gradle thinks it ought to be able to inject something
but I’m not sure what this parameter is!
it seems that calling copy {} from inside the TaskAction is what causes the failure.
e
I believe it will all work fine if you define your classes in a .kt file (in an included build or buildSrc), but inside .kts things take a magic reference to the containing script
p
ahh 😕
e
if you write 
project.copy {}
instead of 
copy {}
then that reference shouldn't be necessary
p
ohh. And that’s just my poor understanding of gradle. Didn’t notice that copy was a method on ProjectDelegate, not Task.
thanks. That solves that mystery.
yup, that did it. Thanks @ephemient!
v
It's not so much magic and not Gradle specific. Things in a Kotlin script get compiled into a class, so if you define a class within the script it is an inner class. If in that inner class use something from the script, a reference to that outer class is necessary. If you use 
project.
, the project is taken from the task, so no reference to the script.
p
makes sense.
e
in a normal class, you can't access the outer scope unless you explicitly write 
inner class
; that's not how top-level classes in .kts work though
74 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by