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

Gradle Community

I have a custom ValueSource that takes an ConfigurableFileCollection as a parameter. Does Gradle support task dependencies for ValueSources?

```internal abstract class GripEnvValueSource : ValueSource&lt;Map&lt;String, String&gt;, Parameters&gt; {
    interface Parameters : ValueSourceParameters {
        val apiFiles: ConfigurableFileCollection
    }
    
  override fun obtain(): Map&lt;String, String&gt; = buildMap {
        for (apiFile in parameters.apiFiles) {
            for (createdFlow in Json.decodeFromString&lt;List&lt;CreatedFlow&gt;&gt;(apiFile.readText())) {
    }}}```

When I wire the apiFiles like this:
```providers.of(GripEnvValueSource::class) {
        parameters {
            apiFiles.from(configurations.foo)
        }
    }```
I still get the error when consuming the ValueSource: File does not exist

If you use a value source, then probably because you want to determine something that should count as CC input right?

That means the value is determined at configuration time

I „just“ want to simplify my task by moving some code to valuesources :melting_face: 

So you are *not* using the value source for CC?
How do you use it? 
I might not have understood the use-case right yet

Not explicitly, but it is a task input so CC relevant. The idea was to create a task accepting a ListProperty<String> and you can use a value source to configure the list via a file (that is a outcome of another task).

So as a workaround I will move the code back to the task

Yeah, I don't think it would work, especially not with CC.
IIRC, when CC is persisted all the providers that are task state are evaluated and the result persisted. 
So the task outputs would not yet be available.

yeah, after talking about it, it sounds impossible :duck:

&gt; Does Gradle support task dependencies for ValueSources?
No, no task dependencies at the moment.

&gt; to configure the list via a file (that is a outcome of another task).
It isn't clear why you need a ValueSource for that. When dealing with task outputs, you can have something like `producerTaskProvider.flatMap { it.outputFileProvider }.map { readStringList(it) }` and use it as a value for the `ListProperty` of the consuming task. It will bring task dependencies along. CC is aware of task outputs and won't evaluate these providers when storing the cache, but will record the transformation  instead.
The only thing to be mindful of is <https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:not_yet_implemented:accessing_top_level_at_execution> when declaring `readStringList`.

The reading and parsing of the file requires another library that should not be part of the plugin classpath but using an isolated classpath from a workerexecutor, but there is also no worker executor option for a valuesource yet. 