dependencyReport up-to-date after changing dependencies in build.gradle


(crotwell) #1

In tracking down a dependency problem, I was editing build.gradle, running gradle dependencyReport, looking at the report, and repeating. Only after several cycles when frustration set in did I realize that the up-to-date check for the dependecyReport task was reporting “UP-TO-DATE”. So I was still looking at the original dependency report instead of one based off of my changes. Grumble, grumble.

I know gradle can have inputs that are “configured items” in addition to just files, so could the dependecyReport have the actual dependencies be its inputs, forcing the task to run after a user edits the dependencies in the build.gradle file?

It just seems that dependencyReport shouldn’t be considered up to date if I just made a change to the dependencies.

thanks, Philip