Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: 209.147.113.130 is neither permitted
 nor denied by domain of mmcgrady@topiatechnology.com)
Subject: Re: JVM version policy Was: Re: Build failed in Hudson:
 River-trunk-jdk1.5 #3
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/mixed; boundary=Apple-Mail-27--504365918
From: MICHAEL MCGRADY <mmcgrady@topiatechnology.com>
In-Reply-To: <DD7CFB39-1342-48B3-BFA8-A7E6AE1B248D@gmail.com>
Date: Thu, 2 Dec 2010 16:17:26 -0800
Message-Id: <AFB8B243-D5CD-488B-B856-7B03501AF3B9@topiatechnology.com>
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>
 <5B911FAB-8614-40A1-BAF4-7D871B16E2DD@gmail.com>
 <F83750A5-E023-466A-8B8F-A3620DBE7786@topiatechnol
  ogy.com> <090E8D39-F125-486A-BB59-1EED4BCD695A@gmail.com>
 <371F7962-68FE-447B-B2B3-7C084C56DD8C@topiatechnology.com>
 <D10CAD2C-1FAD-49FD-AF85-CF725ADDE065@gmail.com>
 <12FEECCE-F0AC-4840-B39D-3DDB701E0258@topiatechnology.com>
 <DD7CFB39-1342-48B3-BFA8-A7E6AE1B248D@gmail.com>
To: river-dev@incubator.apache.org

--Apple-Mail-27--504365918
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The status of Real Time Java is not a sentimental matter, but an =
instructive fact of Sun culture. =20

The first thing should be to see is where Java 1.6 might be a plus for =
River.  Can you list these areas?  That would be very helpful.

MG


On Dec 2, 2010, at 3:58 PM, Dennis Reedy wrote:

> Well all sentimentality aside for JSR 1, I still stick with my earlier =
suggestion of:
>=20
> I would encourage that as River moves along it's roadmap, once the =
namespace is changed to org.apache.river, that River mandates 1.6 as a =
baseline. Migration guides and/or utilities can be provided to assist in =
the transition from legacy Jini to River.=20
>=20
> Regards
>=20
> Dennis
>=20
> On Dec 2, 2010, at 545PM, MICHAEL MCGRADY wrote:
>=20
>> If there is a way to move forward and keep River compatible with Java =
1.5, that would be ideal.  We obviously cannot just stand still even =
though Java RTS might for a time.  It is hard to tell at this stage what =
is happening because of the Oracle purchase of Sun and speculation is =
not a thing I like to do.  However, we do know that Java RTS is the =
first Java Community Process, i.e. literally No. 1, and I cannot believe =
that Java would abandon this effort to the dustbin of history.  That =
would not bode well for Java as a platform. =20
>>=20
>> MG
>>=20
>>=20
>> On Dec 2, 2010, at 2:00 PM, Dennis Reedy wrote:
>>=20
>>> If you're fine with River 2.1.1 then you have a platform which you =
can move forward with right? That release is baselined at Java 1.4.
>>>=20
>>> As River moves forward with it's roadmap, changing the com.sun =
namespace to org.apache, and possibly moving to Java 1.6, you would =
still have a platform (2.1.1) that you could use.
>>>=20
>>> As RTJ (hopefully) moves forward with eventual 1.6+ interoperability =
at that point you could move to River, including product changes to =
account for the namespace change as well.
>>>=20
>>> Does that suffice?
>>>=20
>>> On Dec 2, 2010, at 337PM, MICHAEL MCGRADY wrote:
>>>=20
>>>> More on this later, but I am certainly aware that River cannot stay =
stagnant at Java 1.5.  We need to be realistic but the real-time Java is =
going to "hit" in the near term, I think.  There might need to be =
options and tracks and whatever makes sense to River.
>>>>=20
>>>> MG
>>>>=20
>>>>=20
>>>> On Dec 2, 2010, at 10:42 AM, Dennis Reedy wrote:
>>>>=20
>>>>>=20
>>>>> On Dec 2, 2010, at 127PM, MICHAEL MCGRADY wrote:
>>>>>=20
>>>>>> Perhaps this will help: on the generic question of going to Java =
1.6, and my plea not to do it.
>>>>>>=20
>>>>>> http://www.devx.com/Java/Article/33475
>>>>>=20
>>>>> Michael,
>>>>>=20
>>>>> Thanks for the link. You may also find more information here: =
http://java.sun.com/javase/technologies/realtime/faq.jsp
>>>>>=20
>>>>> One thing on this topic that I am curious about is what Oracle's =
plan is for RTJ. We certainly cant answer that in this forum. But... =
will they keep it? If so, and if they are given a large enough business =
opportunity for it's use, will they move towards supporting 1.6? While =
this is a very interesting and compelling technical use of River, is it =
enough to prohibit River moving to 1.6 and beyond?
>>>>>=20
>>>>> Just asking ...
>>>>>=20
>>>>> Regards
>>>>>=20
>>>>> Dennis
>>>>>=20
>>>>>=20
>>>>=20
>>>> Michael McGrady
>>>> Chief Architect
>>>> Topia Technology, Inc.
>>>> Cel 1.253.720.3365
>>>> Work 1.253.572.9712 extension 2037
>>>> mmcgrady@topiatechnology.com
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>=20
>> Michael McGrady
>> Chief Architect
>> Topia Technology, Inc.
>> Cel 1.253.720.3365
>> Work 1.253.572.9712 extension 2037
>> mmcgrady@topiatechnology.com
>>=20
>>=20
>>=20
>=20

Michael McGrady
Chief Architect
Topia Technology, Inc.
Cel 1.253.720.3365
Work 1.253.572.9712 extension 2037
mmcgrady@topiatechnology.com


--Apple-Mail-27--504365918
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


--Apple-Mail-27--504365918--