Jeff

Would this issue include making it more convenient for one task to depend on the aggregate of all artifacts of a certain type declared in any project? I put more...

Thanks - I was wondering about this too, and the key I noticed for json-20231013.pom seems to match the one you mention in this issue

Also note that this TaskUpToDateValidator was how AndroidX caught some nondeterminisms in our build upon upgrading to Gradle 6.6.1 ( https://issuetracker.google.com/issues/167569304#comment1 ) This observation led to reporting this Gradle bug:...

Another problem we detected via this validation: https://github.com/gradle/gradle/issues/16962

It looks like version 6.1 of Gradle introduces [OperationCompletionListener](https://docs.gradle.org/current/javadoc/org/gradle/tooling/events/OperationCompletionListener.html) , which can listen for FinishEvent's, each of which has a result, and some of those results are of type [TaskExecutionResult](https://docs.gradle.org/current/javadoc/org/gradle/tooling/events/task/TaskExecutionResult.html)...

Also relevant is that we're considering extracting this logic into a plugin that helps with task-up-to-date-validation if others might be interested in it