Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
From: Niclas Hedhman <niclas@hedhman.org>
Organization: Private
To: "Gump code and data" <general@gump.apache.org>
Subject: Re: Avalon Phoenix
Date: Tue, 13 Apr 2004 16:32:27 +0800
User-Agent: KMail/1.5
References: <200404111544.38522.niclas@hedhman.org>
 <m3isg4coe1.fsf@bodewig.bost.de>
In-Reply-To: <m3isg4coe1.fsf@bodewig.bost.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404131632.27312.niclas@hedhman.org>

On Tuesday 13 April 2004 15:45, Stefan Bodewig wrote:
> On Sun, 11 Apr 2004, Niclas Hedhman <niclas@hedhman.org> wrote:
> > Is it possible/recommendable that Gump calls these targets first,
>
> possible?  Yes and you've already done so IIUC.  This will make a
> non-networked Gump run impossible (but there are several other reasons
> why that wouldn't work) and it makes Gump download those jars every
> night.
>
> I wouldn't recommend it but rather try to build the spice stuff from
> sources, if possible.

Phoenix itself is a deprecated container, as a result of Peter Donald's 
ousting and fork. That Phoenix fork is called Loom and is hosted on CodeHaus. 
PeterD has also moved his Spice stuff to CodeHaus, and in the process changed 
the package names. I am not sure if the old sources are still available at 
sourceforge (Spice's old home), and I am more than a little reluctant to 
modify Phoenix sources...

Now, what is the right path forward here?
LeoSimons suggests that I stick the JARs into the Phoenix CVS, which seems 
like a reasonable and straight forward approach.


Advice is appreciated.

Niclas
-- 
+---------//-------------------+
|   http://www.bali.ac         |
|  http://niclas.hedhman.org   |
+------//----------------------+

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org