HI Florian, +1 for moving to Java6.
Once compromise is to wait for one more release with Java5 then move next release with Java6 as release breaking build. If clients for Chemistry need Java5, we could maintain several patch releases for the branch with Java5. Need volunteer from community to merge changes from main to that branch. I think we need to move forward because I have worked with other ASF projects that wait to long to move they just started support generics for Java collections last year. I think we dont want to be in that situation. - Henry On Tue, May 31, 2011 at 12:17 PM, Florian Müller <[email protected]> wrote: > Hi, > > A long, long time ago we decided to compile OpenCMIS with Java 5 and it made > sense at that time. > Today, Java 5 has reached End of Life, Java 6 found its way into even > conservative enterprises and Java 7 is not far away. > > Is there any reason to stick with Java 5 or can we update to Java 6? > > > There are actually a few Java 6 features (for example the CookieManager) that > would help us. > > Any comments? > > > Cheers, > > Florian > -- Thanks, Henry
