[
https://issues.apache.org/jira/browse/CALCITE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336664#comment-15336664
]
Julian Hyde edited comment on CALCITE-1258 at 6/17/16 6:40 PM:
---------------------------------------------------------------
Wow, there are a lot of these "incompatible types" errors.
I don't see how the OpenJDK folks can justify making {{source=1.7}} stricter
than JDK 1.7's javac, even if javac had a bug and didn't comply with the 1.7
language specification. Who cares about compatibility with the 1.7 JLS? I care
about compatibility with the 1.7 JDK.
As a workaround, I'm setting {{souce=1.9 target=1.9}}. Obviously we can't
commit this to master, because we will support 1.7 for a while.
was (Author: julianhyde):
Wow, there are a lot of these.
I don't see how the OpenJDK folks can justify making {{source=1.7}} stricter
than JDK 1.7's javac, even if javac had a bug and didn't comply with the 1.7
language specification. Who cares about compatibility with the 1.7 JLS? I care
about compatibility with the 1.7 JDK.
As a workaround, I'm setting {{souce=1.9 target=1.9}}. Obviously we can't
commit this to master, because we will support 1.7 for a while.
> JDK9 support
> ------------
>
> Key: CALCITE-1258
> URL: https://issues.apache.org/jira/browse/CALCITE-1258
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> I notice that Travis now offers JDK9. Let's get Calcite building & running on
> JDK9.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
