This message was deleted.

Assuming you’re referring to a custom task, the property type for a file would generally be RegularFileProperty.

It is indeed about a custom task or an extension, but configurable by the end-user.

a few options: -have the user directly supply the file, e.g. prop.set(file(“someFile.txt”)) -hide some of that from the user e.g. prop.set(“someFile.txt”) for the extension (as a String), and then taskProp.set(prop.map { layout.projectDir.dir(it))})

Asking for a

String

when configuring an extension would be the most use-friendly – then mapping it to

RegularFileProperty

when passed to the actual task. I’ll stick to that approach, thank you Chris!

You can also accept an Object and use

Project#file

if I understand you correctly. Then the user could choose what to pass you

That’s pretty interesting – but I have bad feelings about it, I’m not sure why.

it’s a hold-over from the very-loosely-typed Groovy heritage of Gradle; cleanest to provide type-safety where possible.

People do still write builds using Groovy 😉

Differently put, this was a recommended practice looong ago, but is bad practice now. ;-)