Hello, I have changing external dependencies in my project. When building the project I noticed that when the dependency is re-downloaded Gradle signals on command line output that all tasks are up-to-date.
I would have expected that if a dependency changes the task is not up-to-date since a major input has changed and may cause build errors. Same behavior I see on changes to the build script itself. Shouldn’t it make also make the up-to-date check resulting in not up-to-date? Thanks, David