I would prefer to keep Java 6 compatibility with Syncope 1.2 and then drop it for Syncope 1.3. Given that this aligns with the probably versions of CXF in both releases, it seems to make sense. Or are there any really pressing reasons to drop compability for Syncope 1.2?
Colm. On Tue, May 20, 2014 at 9:42 AM, Sergey Beryozkin <[email protected]>wrote: > Hi Francesco > > On 20/05/14 08:03, Francesco Chicchiriccň wrote: > >> Hi all, >> this morning I was about to upgrade some dependencies in the trunk >> (mainly due to the fresh release of CXF 3.0.0): while many of them were >> upgraded. I had to give up with Commons DBCP since their latest stable >> release 2.0 requires Java 7 [1]. >> >> Now, since support for Java 6 was dropped a long while ago [1], and >> since I can see many other ASF projects setting Java 7 as their minimum >> requirement (besides Commons DBCP 2.0, also Tomcat >= 8.0, Wicket 7, CXF >> is discussing about this step [3]), I would like to propose to switch to >> Java 7 as minimum requirement for the trunk. >> >> > The only comment about CXF 3.0.0, Dan is planning to branch it out for > Java 6 customers be able to switch to 3.0.0 from 2.7.x, CXF 3.1.0-SNAPSHOT > will be indeed Java 7 based. It is probably not going to affect Syncope, > but mentioning it just in case > > Cheers, Sergey > > > WDYT? >> >> Regards. >> >> [1] http://commons.apache.org/proper/commons-dbcp/ >> [2] https://blogs.oracle.com/java/entry/end_of_public_updates_for >> [3] >> http://cxf.547215.n5.nabble.com/DISCUSS-Short-term-plans- >> branching-td5744177.html >> >> >> > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
