Re: Addressing usability issues with JDK 9-11

I don't see too much difference in taking master as is (e.g. today) vs 2.7 branch. Originally proposed release probably can be named as 2.7.1. Ignite compress also is in master, so for 2.8 it is natural to be master based. Moreover, please take a look at https://issues.apache.org/jira/browse/IGNI

Re: Addressing usability issues with JDK 9-11

It can take more than a month to release from the master. Decent Java 11 support is crucial - the more we delay all the existing usability improvements, the more users we are losing. Check my original email - everyone stumbles upon those gaps. - Denis On Mon, Mar 4, 2019 at 10:51 PM Dmitriy Pavl

Re: Addressing usability issues with JDK 9-11

Previously we've discussed that 2.8 will be a separate release with services redesign. I feel it makes more sense to take master because is contain a number of features, e.g. services, new hibernate version support, more stabilization done. So I suggest taking the master as our base branch for 2.

Re: Addressing usability issues with JDK 9-11

Dmitriy and Dev, Let's release Java 9 - 11 improvements that are already merged? In my understanding, they address or soothe usability issues reported in the original email. I would take Ignite 2.7, merge the changes there and roll out 2.8 as soon as we can. - Denis On Tue, Feb 5, 2019 at 10:2

Re: Addressing usability issues with JDK 9-11

Dmitry, Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-11216 Artem Budnikov reproduced the issue on Linux. - Denis On Mon, Feb 4, 2019 at 8:07 AM Dmitriy Pavlov wrote: > Igniters, > > I've created https://issues.apache.org/jira/browse/IGNITE-11189 as the > main > task to li

Re: Addressing usability issues with JDK 9-11

Igniters, I've created https://issues.apache.org/jira/browse/IGNITE-11189 as the main task to link particular steps to be done. 'Blocked by' link type is for mandatory changes, 'relates to' - for desirable. BTW, examples seem to be running, the only reason they failed was missed dependencies in s

Re: Addressing usability issues with JDK 9-11

Dmitry, thanks for driving this. 1. Startup of a node using both ignite.sh and ignite.bat works for Windows, > OpenJDK 10.0.2. Failure from Denis still needs to be checked by MAC OS > Users. That's easy to reproduce - you need a machine with Mac OS Mojave and latest Oracle JDK - "java version "1

Re: Addressing usability issues with JDK 9-11

Hi Igniters, 0. Results of TC Nightly Run All on Java 11 can be found here https://ci.ignite.apache.org/viewLog.html?buildId=2963881&buildTypeId=IgniteTests24Java8_RunAll

Re: Addressing usability issues with JDK 9-11

Hi Denis, yes, I definitely will close some of these points, I hope Peter I will help with control.sh fix. Point 0. in my plan is to check TeamCity results for Java 11 Run. Unfortunately, I don't have MAC OS so I would appreciate some of MAC users may double check launch issue. Please note it ma

Re: Addressing usability issues with JDK 9-11

Alright, That's what needs to be done: 1. Fix sh/bat scripts work - fails on my Mac OS Mojave and latest Oracle JDK - java version "11.0.2" 2019-01-15 LTS 2. Change command line startup to output warning to stdout and logs to add necessary params to JVM 3. Make sure that examples c

Re: Addressing usability issues with JDK 9-11

The only way to run examples without annoying parameters setup is to use IntelliJ Idea templates. I guess other IDEs have a similar feature. I've described it here https://github.com/apache/ignite/tree/ignite-11140/examples#running-examples-on-jdk-91011 If anyone knows how to declare such defaul

Re: Addressing usability issues with JDK 9-11

I've checked examples from our nightly build from TC. Pom itself was detected normally, I use IntelliJ Idea Ultimate Edition 2018.2. But it can't compile both for Java 8 and for Java 11. I created https://issues.apache.org/jira/browse/IGNITE-11140 so I will come back with fix proposals later. вт

Re: Addressing usability issues with JDK 9-11

Hi Denis, I'm not sure that pom detection is related to Java version or to Ignite. I will check examples. I've checked Apache Ignite TC Bot can be successfully launched using instructions in https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 using OpenJDK

Addressing usability issues with JDK 9-11

Igniters, I played with the latest Oracle JDK 11 on Mac OS Mojave. Results are sad: - Starting a node from cmd (ignite.sh) - FAILED - Opening Ignite examples - BAD EXPERIENCE - pom.xml wasn't detected automatically, had to select it manually - was hard to start the code samples