Thanks for the suggestion, @slustbader. I like it. The question would be how to deal with intermediate nodes in the graph that don't satisfy the predicate. It maybe doesn't apply to your problem, but in general a third-party module could depend on one of your organization. Would you leave them completely out of the graph? Or, only if the complete sub-graph doesn't satisfy the predicate?

For my purposes, I would think filtering out any artifacts that don't match the predicate and then pruning any disconnected subgraphs would work, although I can't speak to the more general case.

I think I have a likelly feature - please let me know if I should open a new ticket for it or if it is OK.

My need is to list only an artifact and all its dependencies (especially in tree view, both children and parents, so also dependencies with different orga/name). My need happen when I'm looking for not needed dependendies to exclude, or trying to understand why some artifact comes into the final dep graph (ex: java logging hell).

A complementary feature would be to be able to use "whatDependsOn" without the version number.

Hello @fanf, @jrudolph.
Sorry for opening an old thread. This is my first request on GitHub.
I had the same requirement in our organisation where we have different modules packed into jar files and which are then used as sbt dependencies. I was looking up to find a way of getting a graphical representation of how the dependencies relate to each other and found your plugin.
Since our jars have a unique organisation name I was able to write down some code which works on the created dependency.dot file and generate .js file with only reference to our dependencies.
What would be the best way to get this incorporated in your plugin? I don't want to create a new plugin just to get this working (though I dont mind creating one).
Any information on this would be great.

Thanks,
Deven Bairat