+1 for pulling the plug on Java 5 in trunk. We are on a major release boundary with 2.0, so now would be the time to do it.
Moving to Java 6: (good) - Meets JPA 2.0 JSE 6 annotation processing requirement - Fewer Java versions to support (and less confusion regarding build vs. runtime Java version requirements) - The ability to naturally (no version checks, reflection, etc.) use new Java 6 features such as JDBC 4 Continue providing compile support for Java 5: (bad) - Additional requirement of making sure OpenJPA builds on both versions of Java - Inability to easily use new Java 6 features without version checks and such - Multiple code paths to maintain for version specific code I agree that if we pull the plug on Java 5, there should be some sort of announce & time period that gives folks ample time to prepare. One or two months seems reasonable. -Jeremy On Thu, Mar 26, 2009 at 10:01 AM, Kevin Sutter <[email protected]> wrote: > Per the discussion with OPENJPA-5 [1], the question of continuing support > of > building with Java 5 has been brought up. Due to the annotation processing > that will be required for JPA 2.0, the use of Java 6 will become a > requirement for trunk. But, do we have to continue to support building > with > Java 5. Pinaki has recently committed changes to allow building with > either > Java 5 or Java 6, but these changes will affect our code path as it relates > to connection processing. So, should we bite the bullet and pull the plug > on Java 5 from a build perspective? This would be for trunk (JPA 2.0) only > and beyond. > > Comments, suggestions, complaints are all welcome. > > Thanks, > Kevin > > [1] https://issues.apache.org/jira/browse/OPENJPA-5 >
