Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 8394 invoked from network); 23 Mar 2004 09:59:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Mar 2004 09:59:14 -0000 Received: (qmail 27115 invoked by uid 500); 23 Mar 2004 09:58:48 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 27013 invoked by uid 500); 23 Mar 2004 09:58:48 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 26998 invoked from network); 23 Mar 2004 09:58:48 -0000 Received: from unknown (HELO smtp.noos.fr) (212.198.2.115) by daedalus.apache.org with SMTP; 23 Mar 2004 09:58:48 -0000 Received: (qmail 9377 invoked by uid 0); 23 Mar 2004 09:59:00 -0000 Received: from unknown (HELO apache.org) ([212.198.17.4]) (envelope-sender ) by 212.198.2.115 (qmail-ldap-1.03) with SMTP for ; 23 Mar 2004 09:59:00 -0000 Message-ID: <40600B2E.8030600@apache.org> Date: Tue, 23 Mar 2004 11:02:22 +0100 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gump code and data Subject: Re: [GUMP][PATCH] Add avalon-framework impl classes References: <40600319.9060807@apache.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed 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 Stefan Bodewig wrote: > On Tue, 23 Mar 2004, Stephen McConnell wrote: > > >>I'll be digging into the remaining cocoon/avalon dependencies this >>week > > > Thanks a lot. > > >>That should get the coocoon depedencies green across the board. > > > For the "old, traditional" Gump builds, they already are. I can't see > why there should be any dependency on fortress in Cocoon. Cocoon > doesn't state one and I don't see a path that would make it an > inherited dependency. I'm guessing its related to the following: cocoon --> excalibur-xmlutil --> excalibur-meta-sourceresolve --> fortress (tools and container) And I figure that excalibur-xmlutil can probably be linked to the excalibur-sourceresolve thereby eliminating the fortress dependency. Stephen. -- |------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------| --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org