You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/02/24 14:32:28 UTC

[jira] Resolved: (OPENJPA-1520) Move trunk (2.0.x) to require Java 6 to build (but target 1.5 runtime)

     [ https://issues.apache.org/jira/browse/OPENJPA-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods resolved OPENJPA-1520.
-----------------------------------

    Resolution: Fixed

So, the final decision was to require 1.6 or later to build but still configure maven-compiler-plugin to target 1.5.  Also, you can build and run the tests with a 1.5 JDK, by using the -Ptest-java5 profile (which the junits are still passing with both the Sun 1.5 JDK and IBM 1.6 SDK using Derby.)

> Move trunk (2.0.x) to require Java 6 to build (but target 1.5 runtime)
> ----------------------------------------------------------------------
>
>                 Key: OPENJPA-1520
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1520
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>    Affects Versions: 2.0.0-beta
>            Reporter: Kevin Sutter
>            Assignee: Donald Woods
>             Fix For: 2.0.0
>
>         Attachments: openjpa-1520.patch
>
>
> http://n2.nabble.com/DISCUSS-Drop-build-support-for-Java-5-td2539470.html#a2540533
> We've had the discussion about dropping Java 5 support (build and runtime) from trunk.  The above referenced string of notes indicates a favorable response.  Before we do an official 2.0.0 release, we should make this change.
> Besides the build aspects, I believe we still have some Java 5 runtime implications in our runtime as well -- some reflection processing due to the jdbc4 support.  We should clean that up as well.
> I've talked to Donald about this and he's game to start this process, but please contribute ideas and testing as you see fit.  Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.