Dan Fabulich wrote:
Oleg Gusakov wrote:
SAT based resolver in the sandbox branch works differently from the
old one, and as such - it may break a few builds that rely on bugs in
the old resolver.
I think we know it will break builds that rely on bugs in the old
resolver, right?
Yes.
And we need to test is more thoroughly.
What sort of testing do you have in mind, exactly? Just general
testing out in the field? Field testing won't necessarily get us that
much if we know that we're going to break builds that rely on bugs.
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.
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
Thanks,
Oleg
-Dan
---------------------------------------------------------------------
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]
