[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798938#comment-16798938
]
Peter Ivanov edited comment on IGNITE-11600 at 3/22/19 11:51 AM:
-----------------------------------------------------------------
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
Also that hack's with {{—add-exports}} can no longer work from JDK to JDK, as
it was between 9 and 11.
was (Author: vveider):
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
> Fix launch script for Java 12
> -----------------------------
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
