Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 59605 invoked from network); 19 May 2007 00:37:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 May 2007 00:37:32 -0000 Received: (qmail 54947 invoked by uid 500); 19 May 2007 00:37:32 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 54877 invoked by uid 500); 19 May 2007 00:37:31 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 54866 invoked by uid 99); 19 May 2007 00:37:31 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 17:37:31 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=DATE_IN_PAST_06_12 X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [72.26.105.135] (HELO goku.simulalabs.com) (72.26.105.135) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 17:37:24 -0700 Received: from [192.168.237.213] (unknown [192.168.237.213]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by goku.simulalabs.com (Postfix) with ESMTP id 31E208F000C for ; Fri, 18 May 2007 17:36:53 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: <50694DDB-3CAC-41BD-B056-0B3ED1B02403@apache.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Brett Porter Subject: Re: [m2] Conflict resolvers Date: Fri, 18 May 2007 10:26:43 -0700 To: "Maven Developers List" X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org As it turned out, we didn't talk about the artifact resolution mechanism in great detail. Jason told us he is working on a paper to describe how it might be re-implemented in 2.1. Jason, any chance you could push what you have into SVN so we can provide some feedback and see how it might line up with Mark's work? If it is compatible, and the patch is good, then we could apply that to trunk now. Either way, I don't think applying this on 2.0.x is a good move. We have to draw the line about new features getting added there. Thanks! - Brett On 17/05/2007, at 10:06 AM, Mark Hobson wrote: > On 30/04/07, Brett Porter wrote: >> As Mark further explained, I think his proposal is entirely different >> and could be adapted to whatever strategy you apply in general here. > > Was there any consensus on whether to apply MNG-612 to 2.0.x after all > the conferences? > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org