[jira] [Commented] (JDO-750) Change development environment to JDK 1.8
[ https://issues.apache.org/jira/browse/JDO-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102142#comment-15102142 ] Craig L Russell commented on JDO-750: - Considering the additional query features of jdo-next (whatever we call it: 3.2 or 4.0) and the requirement for new time types: I'd propose users who need java7 to continue to use 3.1. Anyone who wants the new features will need to move to java 8. > Change development environment to JDK 1.8 > - > > Key: JDO-750 > URL: https://issues.apache.org/jira/browse/JDO-750 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen > Fix For: JDO 3.2 > > > The idea is that we continue to support JDK 1.7 runtime, but the development > requires JDK 1.8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Minutes: JDO TCK Conference Call Friday January 15, 9 AM Pacific Time (PST)
Attendees: Michael Bouschen, Craig Russell Agenda: 1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log 2. New patch on JIRA JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747 Need feedback on the patches and the proposed spec update. The test cases need to be adjusted to meet the specification once the specification changes have been reviewed and agreed. And feedback on the changes needed to the Reference Implementation will also be useful. The new test for OptimisticCheckConsistency can be reviewed first, to be sure that the end goal of recovering from write/delete failures is covered. 3. Other issues Java 7 v. Java 8: https://issues.apache.org/jira/browse/JDO-750 Action Items from weeks past: [Oct 30 2015] AI Craig: File a maintenance review with JCP [May 15 2015] AI Craig Spec change for roll back an active transaction when closing a persistence manager (JDO-735) [Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP Maintenance Release for JDO 3.1 is published [Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651? [Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712 [Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625 [Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
[jira] [Commented] (JDO-750) Change development environment to JDK 1.8
[ https://issues.apache.org/jira/browse/JDO-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102229#comment-15102229 ] Andy Jefferson commented on JDO-750: No objections from me. DN 4.2 supports all features of JDO.next prior to the time types, and allows java7+. DN 5.0 is proposed to use java8 minimum to match JDO.next requiring java8. Consequently anyone using java7 can use DN 4.2 (including new features) or DN 4.1 (with JDO 3.1), and anyone using java8 can use DN 4.1/2 (JDO3.1) or DN5.0 (JDO.next). > Change development environment to JDK 1.8 > - > > Key: JDO-750 > URL: https://issues.apache.org/jira/browse/JDO-750 > Project: JDO > Issue Type: Task > Components: api, tck >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen > Fix For: JDO 3.2 > > > The idea is that we continue to support JDK 1.7 runtime, but the development > requires JDK 1.8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
