This was my understanding also, although there remained some discussions that needed having regarding how we can support other platforms (1.4?, CDC?)
I vaguely recall that we'd make some code changes up to 1.5, but until the above had been resolved such things were to be kept safely in branches... But don't quote me, I might just have invented that bit! On Wed, Dec 29, 2010 at 9:37 PM, MICHAEL MCGRADY <mmcgr...@topiatechnology.com> wrote: > I thought that the discussion did not bleed out but that it reached a limited > consensus that River would go to Java 5 but not presently to Java 6. There > was no formal vote. > > MG > > > On Dec 29, 2010, at 10:40 AM, Sim IJskes - QCG wrote: > >> On 29-12-10 17:49, Niclas Hedhman wrote: >>> On Wed, Dec 29, 2010 at 2:37 PM,<jgr...@simulexinc.com> wrote: >>> >>>> Replacing iterator usage with the enhanced for loop (for each). >>>> Added generic usage to internal methods/fields. (Internal use appeared to >>>> be non-controversial, and might ease future development.) >>>> Removed unused imports. >>> >>> I am curious; Has there been a "move to Java 5" decision already?? >> >> No formal vote has been cast. The discussion just bled out. >> >> Shall we go for a formal vote? >> >> Gr. Sim >> > > Michael McGrady > Chief Architect > Topia Technology, Inc. > Cel 1.253.720.3365 > Work 1.253.572.9712 extension 2037 > mmcgr...@topiatechnology.com > > > >
