Is a pattern like this valid?

@OutputDirectory val outputDir: Property<Directory> = objects.directoryProperty()

@Internal
val outputFile: Provider<RegularFile>
    get() = outputDir
        .map { it.file("SharedGroovyCode.groovy") }

outputDir

is the main output here, and

outputFile

is just an accessor to more conveniently access a subset of that output downstream.

yes. this is useful to encapsulate logic & hide the Property state (Provider is nicely read-only).

thanks! bit weird the naming is

@Internal

if it can expose outputs as inputs to other tasks

But why

Property<Directory>

and not

DirectoryProperty

?

Good point!