Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 23239 invoked by uid 500); 14 Mar 2003 13:22:47 -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 23227 invoked from network); 14 Mar 2003 13:22:46 -0000 Received: from fo1.kc.aoindustries.com (HELO www1.kc.aoindustries.com) (209.15.201.17) by daedalus.apache.org with SMTP; 14 Mar 2003 13:22:46 -0000 Received: from apache.org ([66.208.12.130]) (authenticated) by www1.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id h2EDMlG26447 for ; Fri, 14 Mar 2003 07:22:47 -0600 Message-ID: <3E71D7A6.6060707@apache.org> Date: Fri, 14 Mar 2003 08:22:46 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Spice Dependency (was: RE: Spice License) References: <004701c2e944$eec45f50$0801a8c0@Lagrange> <200303132207.33437.peter@realityforge.org> <3E71BBA6.3020706@apache.org> In-Reply-To: <3E71BBA6.3020706@apache.org> 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 Stefano Mazzocchi wrote: > I think the most important thing is to get Gump to work. Since it > appears that you are very concerned about back-compatibility issues, > what prevents you from helping out to make gump work right for avalon > and specifically excalibur? I am addressing GUMP, and have been for the past few days. It is a frustratingly slow turn around time--and I have a feeling that there are two GUMP repositories--and the one that cvs.apache.org uses is not the one nagoya.apache.org/~rubys uses. I would like to point out that there are *much* fewer compilation problems listed here: http://nagoya.apache.org/~rubys/gump/ Which is where I see my changes happening. Cocoon has a problem in the gump descriptor where the jar file I am trying to reference isn't comming through. Hopefully the next run will let me see a clear cocoon build the next time it is run. I have not been able to get gump running locally, so I have to wait *hours* to see the effects of my changes. To note: Jakarta JAMES is building!!!! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org