river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From MICHAEL MCGRADY <mmcgr...@topiatechnology.com>
Subject Re: JVM version policy Was: Re: Build failed in Hudson: River-trunk-jdk1.5 #3
Date Thu, 02 Dec 2010 20:37:24 GMT
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.


On Dec 2, 2010, at 10:42 AM, Dennis Reedy wrote:

> On Dec 2, 2010, at 127PM, MICHAEL MCGRADY wrote:
>> Perhaps this will help: on the generic question of going to Java 1.6, and my plea
not to do it.
>> http://www.devx.com/Java/Article/33475
> Michael,
> Thanks for the link. You may also find more information here: http://java.sun.com/javase/technologies/realtime/faq.jsp
> 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?
> Just asking ...
> Regards
> Dennis

Michael McGrady
Chief Architect
Topia Technology, Inc.
Cel 1.253.720.3365
Work 1.253.572.9712 extension 2037

View raw message