From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Property is the right way.
You can only inject into the constructor what is an injectable service by Gradle.
But I'd use
```abstract val jvm: Property&lt;Boolean&gt;```
Dunnot what `Delegates.notNull` does.

I'm using `jvm` to return the corresponding `targetDir` later on
```@get:Input
abstract val jvm: Property&lt;Boolean&gt;

@get:OutputDirectory
val targetDir: DirectoryProperty
    get() {
        val platform = if(jvm.get()) "jvm" else "nonJvm"
        val dir = project.layout.buildDirectory.dir("generated/$platform")
        return project.objects.directoryProperty().convention(dir)
    }```
```val generateJvmCode by registering(GenerateCode::class) { jvm.set(true) }
val generateNonJvmCode by registering(GenerateCode::class) { jvm.set(false) }
kotlin.sourceSets {
    named("jvmMain") { kotlin.srcDir(generateJvmCode) }
    named("nativeMain") { kotlin.srcDir(generateNonJvmCode) }
//    named("jsMain") { kotlin.srcDir(generateNonJvmCode) }
}```
however, on sync:
&gt; com.intellij.openapi.externalSystem.model.ExternalSystemException: Could not create task ':generateJvmCode'.
&gt; Could not create task of type 'GenerateCode'.
&gt; Cannot query the value of task ':generateJvmCode' property 'jvm' because it has no value available.
is a dependency between properties allowed?

solved this way
```abstract class GenerateJvmCode : GenerateCode(true)
abstract class GenerateNonJvmCode : GenerateCode(false)

abstract class GenerateCode(
    @Internal
    val jvm: Boolean): DefaultTask() {```


```
@get:Inject
abstract val layout: ProjectLayout

@get:Input
abstract val jvm: Property&lt;Boolean&gt;

@get:OutputDirectory
val targetDir = jvm.flatMap {
    val platform = if (it) "jvm" else "nonJvm"
    layout.buildDirectory.dir("generated/$platform")
}```


is it mandatory for `layout` to be extracted into a property itself?

No, but it is better to inject it and use it than to use `project` usually.
Accessing `project` of a task during configuration time is ok, during execution time it is deprecated and will be forbidden.
So better to simply avoid using it whenever possible.