Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of cgfulton@gmail.com designates
 209.85.213.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=ft+xpeXbz+DPVtRk+qEEGXm6Xd8PHzRX5Qk7zTTtoKN1Ne6qeAg5ne9+dDyZIHBWE0
         2EyZFPOVqJlDZ7xcATpprln/GbwghobfetZ2Rqmf8CN1NwI2MxRXQuxwEnfqE0nEtcRD
         lYhKJdQ5ZXD2Zh4hAD0VpsvzDXBxN5GrcyGp4=
MIME-Version: 1.0
In-Reply-To: <4CF7B534.2010705@qcg.nl>
References: <862502422.8331290517859184.JavaMail.hudson@aegis>
	<112459958.8391290520715806.JavaMail.hudson@aegis>
	<4CEBDFC0.90506@qcg.nl>
	<AANLkTi=x13MS-gUsXMEWyrsm8UjCY-ghpTmO1WnQ+yjt@mail.gmail.com>
	<4CEBE8B0.2020806@qcg.nl>
	<4CEBED3F.3080504@acm.org>
	<77F1E32F67C8D5479858C0C7E93EB46503E19BB8@WAL-MAIL.global.avidww.com>
	<4CEC61DA.3030702@zeus.net.au>
	<4CECC1A5.7070804@qcg.nl>
	<4CED1D08.3030101@acm.org>
	<4CED23EA.1020208@qcg.nl>
	<4CF6688A.7070201@wonderly.org>
	<4CF685DA.3080000@acm.org>
	<4CF6D8B8.6090006@zeus.net.au>
	<4CF6E337.4050402@acm.org>
	<F5422BBB-9F0C-4936-AAF6-A90969644E3B@gmail.com>
	<4CF6F077.7030704@acm.org>
	<84380CFD-746A-4F3C-9F53-E1B2493CF71F@topiatechnology.com>
	<1291266017.16266.3373.camel@cameron>
	<75124B2C-1116-4A35-A186-FDA769E0BC52@topiatechnology.com>
	<EDBE9047-7BA9-4B1C-82F9-AE955428F5AE@gmail.com>
	<F6F627CF-062A-4425-973E-1B311858653D@topiatechnology.com>
	<4CF7B534.2010705@qcg.nl>
Date: Thu, 2 Dec 2010 07:22:00 -0800
Message-ID: <AANLkTi=jHpVw-zgri=DXwTtNR65T6AWt1HWmvHbKLjoW@mail.gmail.com>
Subject: Re: JVM version policy Was: Re: Build failed in Hudson:
 River-trunk-jdk1.5 #3
From: Gerard Fulton <cgfulton@gmail.com>
To: river-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=001517511460b90bd404966efb33

--001517511460b90bd404966efb33
Content-Type: text/plain; charset=UTF-8

I think that Peter correct. River can potentially support both Java 1.5 and
1.6 in the future by implementing a modular build environment and using a
profile/API approach. In my opinion the fact that the Jini community refused
to address this issue was a serious black eye for the project.

Gerard


On Thu, Dec 2, 2010 at 7:03 AM, Sim IJskes - QCG <sim@qcg.nl> wrote:

> On 02-12-10 15:58, MICHAEL MCGRADY wrote:
>
>> There are no RT requirements for River.  There is only the requirement
>> that, if River wants to be compatible with Java RT that it not go to Java
>> 1.6 but stick at Java 1.5.
>>
>
> No matter what the outcome is of the version debate, i would like to
> see/explained a way/method to verify the compatibility.
>
> You cannot ask a developer to run on anything less then JDK6 nowadays. You
> can ask a developer to keep to certain compatibility conventions. In order
> to guard against mistakes, we need a (preferably) automated method of
> verifying if the code produced is still compatible.
>
> When we argue for a certain version, shall we include the verification
> solution with it?
>
> Gr. Sim
>
> --
> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>

--001517511460b90bd404966efb33--