Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v618)
In-Reply-To: <59BA635A-C04F-11D8-BD96-000A958B684A@outerthought.org>
References: <40D07D24.1090309@reverycodes.com> <40D07FF1.9070907@umn.edu>
    <35456.10.0.0.5.1087411978.squirrel@10.0.0.5>
    <40D0A31C.8030708@upaya.co.uk>
 <35633.10.0.0.5.1087415370.squirrel@10.0.0.5> <40D15378.1070405@apache.org>
 <8D0AF86A-C044-11D8-BD96-000A958B684A@outerthought.org>
 <94F646C0-C04C-11D8-83CC-000A95C8D3F8@apache.org>
 <59BA635A-C04F-11D8-BD96-000A958B684A@outerthought.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <09E5492A-C070-11D8-83CC-000A95C8D3F8@apache.org>
Content-Transfer-Encoding: 7bit
From: Gianugo Rabellino <gianugo@apache.org>
Subject: Re: Removing groovy
Date: Thu, 17 Jun 2004 17:07:24 +0200
To: dev@cocoon.apache.org


On Jun 17, 2004, at 1:13 PM, Steven Noels wrote:

> On 17 Jun 2004, at 12:53, Gianugo Rabellino wrote:
>
>> Bottom line: unless we leverage a major JDK1.4 advantage (which AFAIK 
>> is not the case in the current codebase), I'd be -1 to a version 
>> upgrade.
>
> How can we leverage what can't be adopted? ;-)

With a proposal, I guess. If someone comes up with a plan of having, say

a) a much better error handling because of the different exception 
treatment;

b) a stable flow implementation;

c) a much faster XSLT rendering because of NIO-aware XSL engines (not 
that I'm aware of);

d) ... something like that improving the core ...

I'd gladly jump on the 1.4 bandwagon. As long as we're talking about 
optional stuff not belonging to the core, I'd rather stick to 1.3 for a 
while.

Ciao,
-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance: http://www.orixo.com