Gradle :project:tasks --all change in behavior?

(Dean Hiller) #1

I used to use “gradle :project:tasks --all” but am trying to upgrade to 5.0 and in the meantime upgraded to 4.10.3. when I run the above command, you can see from the ‘classes’ tasks that it is not telling me it’s dependencies…

classes - Assembles main classes.

of course, as see at ‘classes’ task depends on ‘compileJava’ and ‘processResources’ task

There is an updated answer saying that this no longer works here

BUT when I go to his link here, I can’t seem to find the new way to do it

I don’t care about the performance of listing the dependencies. I only need to do it once to understand the graph that is going on to wire in my plugin correctly.