Folks,
The JDK11 TC tests results is not totally OK but look like the most
issues are related to the tests environment.
e.g. properties, path resolving, class loaders etc.
The core functions and core functions of modules works properly (see TC
run [1]).
We have the umbrella ticket [2] to tr
In general, I'm totally for the plan 2 - make sure Ignite works with Java
11 and release it in October. However, are we sure we'll be ready to adopt
JTA and Hibernate integrations? We can't release having them broken.
--
Denis
On Thu, Sep 20, 2018 at 4:00 PM Vladimir Ozerov
wrote:
> Igniters, w
Not because of Java (here I would like to relax :) ), but because of
- MVCC stabilization
- and service grid availability,
my vote goes to option 2.
But the final decision is up to Nikolay, as release manager. If he agrees
to make a wider-scope release, then ok, let's go to 2.
чт, 20 сент. 2018 г
Dmitry,
Migration to Java 9 started a year ago. In 4 months commercial users will
stop receiving Java 8 updates without buying commercial licence. This may
trigger a wave of migrations inside commercial organizations, sometimes
urgent. And the only migration option would be Java 11, as neither Jav
Hi Vladimir,
Do you know if update notifier can get and record java version from a node
and send it to Apache Ignite site? Or/And what is the most popular version
now?
I guess most existing users will continue to use their current Java, most
likely Java 8. And they will also require a huge amount
