[
https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902332#comment-14902332
]
Andy Jefferson commented on JDO-749:
------------------------------------
So the real question is, is everyone ok with updating the (minimum) JDK that
Apache JDO needs to be developed with to 1.8? (after all 1.7 is past EOL).
With that we can add support for JDK 1.8 types in the API (for JDO 3.2), add
tests for them in the TCK, whilst still releasing jars that have
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
> 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)
