This message was deleted.

If the docs day it just be one of these types, I guess it has to be one of these types. But maybe you can add another property of type

ConfigurableFileProperty

that is derived from your directory list?

ListProperty<Directory>

should work as well if it has the right annotations, e.g.

@InputFiles

and

@Incremental

. The important thing right now is that the value can carry the identity of the property somehow.

Hi @wolfs the use case is to process android source which is a

Provider<List<Directory>>

val androidExtension = project.extensions.getByType(ApplicationAndroidComponentsExtension::class.java)
androidExtension.onVariants { appVariant ->
    val allSources: Provider<List<Directory>> = appVariant.sources.java.all
    val sourceVerificationTask = project.tasks.register<SourceToVerificationCodesTask>(
         "${appVariant.name}SourceToVerificationCodes"
    ) {
        sources.from(project.files(allSources))
        ...
    }
}

abstract class SourceToVerificationCodesTask : DefaultTask() {
    @get:Incremental
    @get:InputFiles
    abstract val sources: ConfigurableFileCollection// ListProperty<Directory>
    ...
}

However the inputChanges.getFileChanges(…) does not accept ListProperty (Check the attached image) @Vampire I think your idea is great~ will try that as well, for now I just wrap the

ListProperty<Directory>

by

project.files()

Ah right, we trimmed down the API. So it seems like

ConfigurableFileCollection

should be the way to go.

Oh, is there any particular reason that the API got trimmed? Just curious.

Mainly because we didn’t expect folks to use a collection property with file system locations but to use

FileCollection

instead.

Thanks both👍