Re: [aether-users] Determining all *possible* dependencies of an artifac

[Benjamin Bentmann <bentmann@xxxxxxxxxxxx>]

Andreas Sewe wrote:

> we are currently facing the problem of determining all *possible*
> dependencies an artifact might have (either directly or indirectly).
> [...]
> As far as I can see, the graph returned by
> RepositorySystem.collectDependencies(..) looks promising, but I am not
> sure whether it is possible to configure the request such that we can
> derive *all* possible paths through the dependency DAG from it or
> whether version ranges have always been narrowed down to one version
> prior to building the DAG.

From your description, it seems you basically want to get the DAG 
before conflict resolution nukes duplicates. In that case, try setting a 
null DependencyGraphTransformer on the RepositorySystemSession you use. 
Be careful though when traversing the DAG returned from 
collectDependencies(), without conflict resolution, it can contain cycles.


Benjamin