[
https://issues.apache.org/jira/browse/IGNITE-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527658#comment-16527658
]
ASF GitHub Bot commented on IGNITE-8859:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4281
IGNITE-8859 - Open upper Java verison bounds
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8859
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4281.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4281
----
commit c474e3e68cae80bd7bf4e2eda69a594bfc4f6e0f
Author: dkarachentsev <dkarachentsev@...>
Date: 2018-06-29T13:16:02Z
IGNITE-8859 - Open upper Java verison bounds
----
> Open upper Java verison bounds
> ------------------------------
>
> Key: IGNITE-8859
> URL: https://issues.apache.org/jira/browse/IGNITE-8859
> Project: Ignite
> Issue Type: Improvement
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Priority: Major
> Fix For: 2.7
>
>
> JDK is going to be release twice a year and it will be always an issue for
> users to start Ignite on newer Java version as we have explicit bounds.
> Ignite should not disallow starting in latest JDK, but show warning that it
> wasn't tested against running version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
