Thanks for the summary mail, Mark. I agree that's the general plan. A
couple of comments...
On 20/06/2007, at 2:48 AM, Mark Hobson wrote:
other than that let's just choose one of the libraries and deprecate
the other one to avoid splitting the work
archiva-dependency-graph appears to be quite tied in to archiva
itself, so I'm not sure how easy it'd be to move away from that.
The
situation so far appears to be:
- maven-dependency-tree uses the 2.0.x core APIs to build the same
tree as Maven actually uses
right
- archiva-dependency-graph is a good proof-of-concept of how
graph-based resolution could be implemented in 2.1, although is
currently quite tied to archiva itself
Yes, it sort of is, but it will surely reuse whatever ends up in
maven 2.1.
- Jason has some code for graph-based resolution in 2.1, which will
supersede and replace the need for maven-dependency-tree
Whatever goes into 2.1 should be usable in Archiva, dependency tree,
maven, and any other tools, yes. I haven't seen Jason's code or spec,
so I can't comment on whether that's the final solution yet :)
I believe maven-dependency-tree is still relevant for 2.0.x and I will
continue to work on it since that's the version I'm targeting. Once
the spec and implementation is done for 2.1, it should be very easy to
move these diagnostic tools over to use that instead.
Makes sense. It's likely we'll still need 2.0.x compatible tools even
after 2.1 is out for some time.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
