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. And we need to test is more thoroughly.
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.
Thanks,
Oleg
Brian E. Fox wrote:
If we are merging in the branch jason/oleg have been working on, then
the issues I mentioned are moot as they occurred in the old code. That
said, I would expect Oleg or Jason to push the release forward given
that they know the full status.
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 1:24 PM
To: Maven Developers List
Subject: maven artifact issues before release
Hi,
I've fixed the code to make double deployment fail properly. Once that
is made configurable, there are no open issues for MARTIFACT 3.0 alpha
1.
MNG-3456, 3617, 3599, 3423, 3352, 3333 are on my list to check next as
they are artifact-3.0 related. I might be short on time for the next
week or so though. But once they are reviewed, I was planning to put
together a release.
Is there anything else to add for a release? Brian - you mentioned
regressions in the number of times resolution occurred?
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
