Hi Kenney,
On 16/06/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
Just a quick question as to what this is for?
maven-dependency-tree is the shared component for computing dependency
trees from Maven's artifact resolution. The original code came from
project-info-reports:dependencies, which I extracted for reuse by
help:dependencies.
Is it used in 'help:dependencies'?
It was, although I've now moved help:dependencies to dependency:tree
after a recent discussion.
Is it/will it be used in maven-core?
It isn't at the moment, but I assume it will be replaced with the
graph based artifact resolution being discussed for 2.1.
I see the dependency plugin uses both dependency-tree and dependency-analyzer,
what's the relation?
dependency-tree is as described above; dependency-analyzer performs a
bytecode analysis of compiled classes and determines which of the
declared and transitive dependencies are actually used.
If maven core eventually uses this, shouldn't it be moved into maven-components?
Possibly, although I'd have thought the new artifact resolution for
2.1 would supersede this.
The help:dependencies goal shows a tree of dependencies, and it didn't work too
well because the algorithm used there didn't match the internal algorithm from
maven itself, so the report was quite useless. Is this an attempt to fix that?
I assume you're talking about MDEP-97. See my comment in that issue,
but yes, the aim for this component is to accurately reflect what is
happening within Maven.
Hope this helps,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
