[
https://issues.apache.org/jira/browse/JDO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902427#comment-14902427
]
Tilmann Zäschke commented on JDO-749:
-------------------------------------
I fully support moving to Java 1.8.
But I'm not sure that it is possible to release source/target JRE 1.7 code
using an 1.8 JDK. At least I used to have problem releasing 1.6 using a 1.7
JDK, and it didn't even contain 1.7 specific code.
Could you clarify how/that 1.8 code can be back-compiled to 1.7?
And something taht is a bit off-topic:
If we really move to a 1.8 API, maybe it would make sense to rediscuss the new
query API. Would it make sense to design it in a way that it is compatible with
the Java 8 streams and possibly lambdas?
> 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)
