Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <40444942.2070507@apache.org>
Date: Tue, 02 Mar 2004 09:43:46 +0100
From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [VOTE] - Entry level JSDK 1.4 in Cocoon 2.2
References: <35548.10.0.0.5.1078112489.squirrel@ags01.agsoftware.dnsalias.com>
 <4042F565.2040208@cbim.it> <4043E1C3.4080002@leverageweb.com>
In-Reply-To: <4043E1C3.4080002@leverageweb.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Geoff Howard wrote:

> Ugo Cei wrote:
>
>> Antonio Gallardo wrote:
>>
>>> Do you agree with JSDK 1.4 as the lower Java version supported in 
>>> Cocoon 2.2?
>>>
>>> Here is my +1
>>
>>
>>
>> -0.5
>>
>> Even though 1.4 is available for most platforms, and I've been using 
>> it exclusively for quite a long time, I still think there are many 
>> environments where people are forced to use 1.3 (not to mention 1.2) 
>> and upgrading wouldn't be an easy task.
>
>
>
> Does anyone here have any direct experience with such a situation?  I 
> am having a hard time imagining a case where a new development effort 
> would be forced for technical reasons not to deploy on a newer 
> backwards compatible jdk.  Old 1.3 code will run (in some cases after 
> recompilation), and old projects can still use whatever jvm version 
> they need.  But a new project based on a new version of Cocoon?  Ok, a 
> 2.1 project may want to upgrade but my experiences have shown 
> upgrading jvm generally painless compared to upgrading Cocoon versions...

Yes I have. But I think it's okay if 2.1 has JDK1.3 as minimum JVM and 
Cocoon 2.2 JDK1.4 because it will take some time until the 2.2 branch 
will be released and marked as stable. And I don't think that those 
organizations use unstable software ;-)

--
Reinhard