This message was deleted.
# plugin-development
s
This message was deleted.
t
I suppose all this is used in some task action?
j
yes
t
probably your task could use more specific types of inputs?
j
Ok, but how? I need to know when my task action is run, which dependencies are applied to the build, and which are present in
gradle/libs.versions.toml
but maybe it isn't at all possible...
t
Have you tried to use
SetProperty<Dependency>
type as task input type for dependencies? And for version catalog
Provider<Iterable<VersionCatalog>>
?
j
Gradle won't create a provider of VersionsCatalog, probably not serializable For the dependencies, I think I need the upcoming feature in 7.5 to depends on the dependency graph in a lazy manner https://github.com/gradle/gradle/issues/12871#issuecomment-1009758750
t
Probably for now you could mark your plugin tasks as non-configuration-cache compatible: https://docs.gradle.org/7.4/userguide/configuration_cache.html#config_cache:task_opt_out
👍 1