On 19/06/2008, at 3:47 AM, 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.
I don't think we're really at that point yet, and regardless we need to know if the other code actually addresses the issue too.
Can you describe what the problem is, or some examples of it? - Brett
-----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]
-- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
