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 <s...@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 >
