Return-Path: Delivered-To: apmail-maven-wagon-dev-archive@www.apache.org Received: (qmail 38891 invoked from network); 30 Mar 2004 21:00:49 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 30 Mar 2004 21:00:49 -0000 Received: (qmail 78831 invoked by uid 500); 30 Mar 2004 21:00:36 -0000 Delivered-To: apmail-maven-wagon-dev-archive@maven.apache.org Received: (qmail 78808 invoked by uid 500); 30 Mar 2004 21:00:36 -0000 Mailing-List: contact wagon-dev-help@maven.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: wagon-dev@maven.apache.org List-Id: "Maven Wagon Developers List" Delivered-To: mailing list wagon-dev@maven.apache.org Received: (qmail 78761 invoked from network); 30 Mar 2004 21:00:36 -0000 Received: from unknown (HELO hogshead.codehaus.org) (66.216.68.111) by daedalus.apache.org with SMTP; 30 Mar 2004 21:00:36 -0000 Received: from [192.168.1.103] (CPE00045a0b555b-CM023080004191.cpe.net.cable.rogers.com [24.102.210.93]) by hogshead.codehaus.org (8.11.6/8.11.6) with ESMTP id i2UL7N510362 for ; Tue, 30 Mar 2004 15:07:23 -0600 Subject: Re: Conductor facade From: Jason van Zyl To: wagon-dev@maven.apache.org In-Reply-To: <1080675241.21604.67.camel@new.brickner.net> References: <1080672151.10774.3294.camel@localhost.localdomain> <1080673078.21604.64.camel@new.brickner.net> <1080673569.10774.3304.camel@localhost.localdomain> <1080675241.21604.67.camel@new.brickner.net> Content-Type: text/plain Organization: Message-Id: <1080680434.10774.3313.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 30 Mar 2004 16:00:35 -0500 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 2004-03-30 at 14:34, Scott Brickner wrote: > On Tue, 2004-03-30 at 14:06, Jason van Zyl wrote: > > No problem, I figured it was only Michal, Emmanuel and myself here :-) > > Nope, I actually think Wagon may be one of the most important projects > out there right now. It takes *way* too long to get any non-trivial bit > of Java code working right now because of the poor handling of > dependencies and weak support for getting the requisite jars. This is true, but Wagon is the artifact/repository layer. The behaviour of pulling in dependencies is the job of the tool that uses Wagon. In our particular case it is Maven. Maven will decide on the policies of dependency satisfying. Just as Maven will house the policies for standard conventions like SNAPSHOTs, conflict resolution and the like. You definitely do not want these notions coupled into the repsoitory/artifact tool. It's just poor design and you'll get the code into a huge mess very quickly. So if it's the dependency resolution aspects you are looking at then the code in maven2 is what you will probably find interesting :-) > So I'm definitely paying attention :) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wagon-dev-unsubscribe@maven.apache.org > For additional commands, e-mail: wagon-dev-help@maven.apache.org -- jvz. Jason van Zyl jason@maven.org http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: wagon-dev-unsubscribe@maven.apache.org For additional commands, e-mail: wagon-dev-help@maven.apache.org