Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 19395 invoked from network); 29 Mar 2004 07:36:35 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Mar 2004 07:36:35 -0000 Received: (qmail 35151 invoked by uid 500); 29 Mar 2004 07:36:11 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 35096 invoked by uid 500); 29 Mar 2004 07:36:10 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 35073 invoked from network); 29 Mar 2004 07:36:09 -0000 Received: from unknown (HELO f2.hedhman.org) (203.121.47.163) by daedalus.apache.org with SMTP; 29 Mar 2004 07:36:09 -0000 Received: from f2.hedhman.org (f2.hedhman.org [127.0.0.1]) by f2.hedhman.org (8.12.8/8.12.8) with ESMTP id i2T7aEEV002081 for ; Mon, 29 Mar 2004 15:36:20 +0800 From: Niclas Hedhman Organization: Private To: "Avalon Developers List" Subject: Re: [GUMP@lsd]: avalon-excalibur/excalibur-instrument-manager failed Date: Mon, 29 Mar 2004 15:36:13 +0800 User-Agent: KMail/1.5 References: <200403290524.i2T5OWT23217@bodewig.bost.de> <200403291520.12226.niclas@hedhman.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403291536.13812.niclas@hedhman.org> 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 Monday 29 March 2004 15:26, Stefan Bodewig wrote: > On Mon, 29 Mar 2004, Niclas Hedhman wrote: > > Sorry that I haven't got around to fix the Gump build yet. > > No problem at all, in particular since other people (me, for example) > could help as well. I just wanted to know which direction has to be > taken in this case. Well, the objectives for the work that was carried out; 1. Removal of all cyclic dependencies and cross-module dependencies. 2. Simple build procedure. That means that Fortress has been moved to "avalon-excalibur" and some internal changes with Fortress. Also the Excalibur Testcase (an abstract class for ECM based tests) was taken out of avalon-excalibur/component into its own subproject. If you do a fresh checkout of "avalon-excalibur", it should now be possible to build every piece of it by a simple; maven multiproject:jar And the ambition is get to a point where other multiproject targets also work, incl :site and :deploy, but I am not there yet. It is also the intention that as little as possible is configured in each subproject, so all build info is collected in the top-level directory. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org