openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milosz Tylenda (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1520) Move trunk (2.0.x) to Java 6 (build and runtime)
Date Thu, 18 Feb 2010 19:06:28 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835339#action_12835339
] 

Milosz Tylenda commented on OPENJPA-1520:
-----------------------------------------

I remember the following:
1. Remove ConcreteClassGenerator usages.
2. Update and simplify JDBC delegates (Delegating* classes) to match JDBC4. Many of them are
currently at JDK 1.3 level throwing UnsupportedOperationExceptions from JDBC3 methods or having
now unnecessary JDBC3 reflection code.
3. Update user manual links to point to JSE6/JEE6 javadocs.


> Move trunk (2.0.x) to Java 6 (build and 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
>
>
> 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.


Mime
View raw message