sbt-dependency-graph is mostly a debugging plugin used in interactive fashion. So, in most cases no configuration should be necessary (like where to put the output). Also, we should be consistent and provide all the output options for every task.
I propose the following convention:
dependencyTree: As it is now, runs the analysis and print its output to the sbt console
dependencyTree::toFile: A new InputTask that allows specifying a filename to safe the output to
dependencyTree::toJsonFile: A new InputTask that allows specifying a filename where the tasks data is printed out in structured JSON form (if available)
dependencyTree::asString: The value itself if you want to use it in your build for other purposes
sbt-dependency-graph is mostly a debugging plugin used in interactive fashion. So, in most cases no configuration should be necessary (like where to put the output). Also, we should be consistent and provide all the output options for every task.
I propose the following convention:
dependencyTree: As it is now, runs the analysis and print its output to the sbt consoledependencyTree::toFile: A new InputTask that allows specifying a filename to safe the output todependencyTree::toJsonFile: A new InputTask that allows specifying a filename where the tasks data is printed out in structured JSON form (if available)dependencyTree::asString: The value itself if you want to use it in your build for other purposes