On 19/06/2008, at 8:36 AM, Oleg Gusakov wrote:
Are there additional tests we could write today?
For SAT based resolver we need to
1). proof-run it against big artifacts (like maven-core, for
instance) and make sure it resolves all the transitives correctly.
Ideally - run against a representative selection from maven-central
and compare results to the old resolver. For now I have tests on
simple mocked artifacts working, need real stuff.
I posted a while back about a tool I wrote that will verify the same
resolution tree for all the POMs in the central repository. It's not
comprehensive, but it's a start - so I'd be happy to get that running
on it once you think it's ready.
2). Develop some range resolution tests
The next release will still use old resolver, but the
intermediate, pre-SAT graph-based solution will be there as an
independent component of artifact, it is used by visualization and
APIs, not by the build.
Do you mean the "next release" of maven-artifact? (2.0.10? 3.0?)
Or the next release of Maven? (2.0.10? 2.1?)?
maven-artifact 3.0
Right, so let me make sure I'm understanding clearly...
3.0-alpha-1: released as is, with or without those few fixes I was
looking at getting in.
3.0-alpha-X: later introduce the mercury and SAT based stuff as an
optional component
3.0: when all the above is stable and the resolution method is
selectable
Is that how everyone sees it going?
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
