Ouput from "dependencies" task interleaved with output from downloads


(Sebastian Schuberth) #1

When using Gradle 2.13 on a project freshly cloned from a Git repository (i.e. it was not built yet, and artifacts were not downloaded to the cache yet), and running ./gradlew project_name:dependencies, the tree output might get interleaved with output from downloading the artifacts. It looks like this:

    pmd - The PMD libraries to be used for this project.
    Download https://jcenter.bintray.com/net/sourceforge/pmd/pmd-java/5.4.1/pmd-java-5.4.1.pom
    Download https://jcenter.bintray.com/net/sourceforge/pmd/pmd/5.4.1/pmd-5.4.1.pom
    Download https://jcenter.bintray.com/net/sourceforge/pmd/pmd-core/5.4.1/pmd-core-5.4.1.pom
    \--- net.sourceforge.pmd:pmd-java:5.4.1
         +--- jaxen:jaxen:1.1.6
         +--- net.java.dev.javacc:javacc:5.0
         +--- net.sourceforge.pmd:pmd-core:5.4.1
         |    +--- com.beust:jcommander:1.48
         |    +--- commons-io:commons-io:2.4
         |    +--- jaxen:jaxen:1.1.6
         |    +--- net.java.dev.javacc:javacc:5.0
         |    +--- net.sourceforge.saxon:saxon:9.1.0.8
         |    +--- org.apache.commons:commons-lang3:3.4
         |    \--- org.ow2.asm:asm:5.0.4
         +--- net.sourceforge.saxon:saxon:9.1.0.8
         \--- org.ow2.asm:asm:5.0.4

I believe that’s a bug as it breaks the tree output and make sit hard to read.


(Mark Vieira) #2

You can avoid the noise with the -q command line argument.


(Sebastian Schuberth) #3

Right. But then -q should be implied by the dependencies task. Otherwise its tree output is pretty much useless, esp. when parsing it further.