Hi,
Just a quick question as to what this is for? Is it used in 'help:dependencies'? Is it/will it be used in maven-core? I see the dependency plugin uses both dependency-tree and dependency-analyzer,
what's the relation? If maven core eventually uses this, shouldn't it be moved into maven-components? 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? -- Kenney Mark Hobson wrote:
Hi there, I've been working on dependency tree diagnostic tools and as a consequence have made substantial changes to maven-dependency-tree. A brief synopsis of changes are: - support for node states: included, omitted for conflict, etc. - node filter API and various implementations for pruning the tree - node visitor API and various implementations for processing the tree (esp. serializing visitor for pretty printing the tree, complete with ascii art :) There's a few API changes for the better, but I assume that's okay. So the question is: can this be submitted as a big patch, or must I painstakingly reverse engineer each change into a set of accumulative patches.. (hint: big patch) Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
