Up-to-date check fails to detect actual dependency changes

[sb-software]

The current Gradle task doesn't seem to take the actual dependency tree into account when determining its up-to-date state. This means any changes made to a project's dependencies will not be detected unless using --rerun-tasks or clean between runs.

Probably trying to keep and evaluate the tree would be as expensive as just always running the task so my initial suggestion would be to simply mark the task as an @UntrackedTask as the task itself doesn't seem that heavy-weight to begin with.

[JakeWharton]

The classpath that we read the dependencies from is marked as a task input so this should not happen. I'll try to see if I can reproduce at some point.