[ https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902561#comment-14902561 ]
Andy Jefferson commented on JDO-749: ------------------------------------ I can add Java 8 classes to a project with those maven compile directives, and have JAVA_HOME set to JDK 1.8 (so using a JDK 1.8 compiler), and do a mvn clean install, and it compiles/installs. At runtime if running with JRE 1.8 and I make use of a LocalXXX class it works fine, and if I'm at runtime with JRE 1.7 then I won't have any LocalXXX class in my persistence capable classes so no problem there either. Since there are no explicit references to the JDK 1.8 classes in any class that a JRE 1.7 user will be instantiating then there is no problem at runtime when using JRE 1.7 (i.e this is a *specific case* of using JDK 1.8 classes without referring to them in non JRE 1.8 code). Admittedly some IDE's have issues with such a setup and the better solution is to go to JRE 1.8 for all; question of timing. And about yet another 'redesign' of the query API, we have waited nearly 3 years for this one from the provision of the DN TypesafeQuery API with little input from others. Bear in mind that I wouldn't be contributing much time, so if you want it then you need to provide time/ideas/implementations/tests. > Support for java.time types, and querying using associated methods > ------------------------------------------------------------------ > > Key: JDO-749 > URL: https://issues.apache.org/jira/browse/JDO-749 > Project: JDO > Issue Type: New Feature > Components: api, specification, tck > Reporter: Andy Jefferson > > Refer to an associated issue for JPA for what support should look like > https://java.net/jira/browse/JPA_SPEC-63 > The methods that should be supported in queries would initially be > LocalDateTime : getDayOfMonth, getMonth, getYear, getHour, getMinute, > getSecond > LocalTime : getHour, getMinute, getSecond > LocalDate : getDayOfMonth, getMonth, getYear > These would need to be part of JDOQL string-based, as well as the > JDOQLTypedQuery (hence have equivalent Expression classes). > Note that all of these are already implemented in DataNucleus, and there are > JDOQLTypedQuery expression classes available. > Timing of this simply depends on the JRE that the next release of JDO is > targetted at, since this needs Java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)