We have seen multiple opinions on this topic now. I think it is fair to conclude that we are not changing the Java version in the next release.
Let me propose something different. We could release three client packages: - A Java 5 package containing 98% of the OpenCMIS features and all dependencies with a warning that this will fade away over time. - A Java 6 package containing all OpenCMIS features and all dependencies. - A Java 7 package containing all OpenCMIS features and a reduced set of dependencies. (Several OpenCMIS dependencies will be covered by the new JRE and we don't have to ship them anymore.) The server packages should move to Java 6. That shouldn't affect too many projects using OpenCMIS. We don't have to do that immediately but we should put it on the roadmap. It would also require some Maven magic that we have to sort out first... WDYT? Florian On 31/05/2011 20:17, Florian Müller 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
