Addressing usability issues with JDK 9-11
Locked
 
|
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 (same issue as with cmd). As a committer, I know how to fix it ( https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11), but most of the developers have no glue and will give up - The step above have to be repeated for every single sample We briefly discussed this with some community managers and our fellows will share the fix plan here. In the meantime - Artem agreed to help on the docs side: https://issues.apache.org/jira/browse/IGNITE-11113 - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner of Ignite website: https://ignite.apache.org/index.html - Denis |
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 10.0.2 on Windows 10. The only issue was with JAXB dependencies, but it is definitely not related to Apache Ignite. BTW, thank you for the banner. Sincerely, Dmitriy Pavlov пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > 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 (same issue as with cmd). As a > committer, I know how to fix it ( > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > ), > but most of the developers have no glue and will give up > - The step above have to be repeated for every single sample > > We briefly discussed this with some community managers and our fellows will > share the fix plan here. > > In the meantime > > - Artem agreed to help on the docs side: > https://issues.apache.org/jira/browse/IGNITE-11113 > - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner of > Ignite website: https://ignite.apache.org/index.html > > > - > Denis > |
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. вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > 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 10.0.2 on Windows 10. The only issue was with JAXB > dependencies, but it is definitely not related to Apache Ignite. > > BTW, thank you for the banner. > > Sincerely, > Dmitriy Pavlov > > пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > >> 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 (same issue as with cmd). As a >> committer, I know how to fix it ( >> >> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 >> ), >> but most of the developers have no glue and will give up >> - The step above have to be repeated for every single sample >> >> We briefly discussed this with some community managers and our fellows >> will >> share the fix plan here. >> >> In the meantime >> >> - Artem agreed to help on the docs side: >> https://issues.apache.org/jira/browse/IGNITE-11113 >> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner of >> Ignite website: https://ignite.apache.org/index.html >> >> >> - >> Denis >> > |
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 defaults using maven on IntelliJ settings, please share. ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > 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. > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > >> 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 10.0.2 on Windows 10. The only issue was with JAXB >> dependencies, but it is definitely not related to Apache Ignite. >> >> BTW, thank you for the banner. >> >> Sincerely, >> Dmitriy Pavlov >> >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: >> >>> 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 (same issue as with cmd). As a >>> committer, I know how to fix it ( >>> >>> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 >>> ), >>> but most of the developers have no glue and will give up >>> - The step above have to be repeated for every single sample >>> >>> We briefly discussed this with some community managers and our fellows >>> will >>> share the fix plan here. >>> >>> In the meantime >>> >>> - Artem agreed to help on the docs side: >>> https://issues.apache.org/jira/browse/IGNITE-11113 >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner of >>> Ignite website: https://ignite.apache.org/index.html >>> >>> >>> - >>> Denis >>> >> |
|
|
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 can be compiled and run with Java 11 4. Make Ignite buildable with Java 11 Points 1-3 are quick. Dmitriy are you the one who is looking into it? When can we release Ignite 2.8. We should do this as soon as possible. - Denis On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email]> wrote: > 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 defaults using maven on IntelliJ > settings, please share. > > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > > > 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. > > > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > > > >> 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 10.0.2 on Windows 10. The only issue was with JAXB > >> dependencies, but it is definitely not related to Apache Ignite. > >> > >> BTW, thank you for the banner. > >> > >> Sincerely, > >> Dmitriy Pavlov > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > >> > >>> 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 (same issue as with cmd). > As a > >>> committer, I know how to fix it ( > >>> > >>> > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > >>> ), > >>> but most of the developers have no glue and will give up > >>> - The step above have to be repeated for every single sample > >>> > >>> We briefly discussed this with some community managers and our fellows > >>> will > >>> share the fix plan here. > >>> > >>> In the meantime > >>> > >>> - Artem agreed to help on the docs side: > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner of > >>> Ignite website: https://ignite.apache.org/index.html > >>> > >>> > >>> - > >>> Denis > >>> > >> > |
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 may be just a warning about illegal-access, even if it is set =permit. After this warning (it is unavoidable for 1st time), everything should be ok. Sincerely, Dmitriy Pavlov чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > 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 can be compiled and run with Java 11 > 4. Make Ignite buildable with Java 11 > > Points 1-3 are quick. Dmitriy are you the one who is looking into it? When > can we release Ignite 2.8. We should do this as soon as possible. > > - > Denis > > > On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email]> > wrote: > > > 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 defaults using maven on IntelliJ > > settings, please share. > > > > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > > > > > 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. > > > > > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > > > > > >> 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 10.0.2 on Windows 10. The only issue was with JAXB > > >> dependencies, but it is definitely not related to Apache Ignite. > > >> > > >> BTW, thank you for the banner. > > >> > > >> Sincerely, > > >> Dmitriy Pavlov > > >> > > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > > >> > > >>> 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 (same issue as with cmd). > > As a > > >>> committer, I know how to fix it ( > > >>> > > >>> > > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > > >>> ), > > >>> but most of the developers have no glue and will give up > > >>> - The step above have to be repeated for every single sample > > >>> > > >>> We briefly discussed this with some community managers and our > fellows > > >>> will > > >>> share the fix plan here. > > >>> > > >>> In the meantime > > >>> > > >>> - Artem agreed to help on the docs side: > > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top banner > of > > >>> Ignite website: https://ignite.apache.org/index.html > > >>> > > >>> > > >>> - > > >>> Denis > > >>> > > >> > > > |
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 <https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv> 19 suites & 580 tests failed. So we need to do one-by-one research for occurred problems. 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. Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs to be fixed. I hope Peter I. will pick up it, fix is quite simple. Details about illegal access and its warning can be found here: http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation 2. Ignition.start warnings: https://issues.apache.org/jira/browse/IGNITE-11155 3. I’ve done some fixes in the https://issues.apache.org/jira/browse/IGNITE-11140 for examples, and I’m going to validate results once our Release is passing. Today’s build failed https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E Sincerely, Dmitriy Pavlov пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > 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 may be just a warning about > illegal-access, even if it is set =permit. After this warning (it is > unavoidable for 1st time), everything should be ok. > > Sincerely, > Dmitriy Pavlov > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > >> 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 can be compiled and run with Java 11 >> 4. Make Ignite buildable with Java 11 >> >> Points 1-3 are quick. Dmitriy are you the one who is looking into it? When >> can we release Ignite 2.8. We should do this as soon as possible. >> >> - >> Denis >> >> >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email]> >> wrote: >> >> > 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 defaults using maven on IntelliJ >> > settings, please share. >> > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: >> > >> > > 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. >> > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: >> > > >> > >> 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 10.0.2 on Windows 10. The only issue was with JAXB >> > >> dependencies, but it is definitely not related to Apache Ignite. >> > >> >> > >> BTW, thank you for the banner. >> > >> >> > >> Sincerely, >> > >> Dmitriy Pavlov >> > >> >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: >> > >> >> > >>> 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 (same issue as with cmd). >> > As a >> > >>> committer, I know how to fix it ( >> > >>> >> > >>> >> > >> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 >> > >>> ), >> > >>> but most of the developers have no glue and will give up >> > >>> - The step above have to be repeated for every single sample >> > >>> >> > >>> We briefly discussed this with some community managers and our >> fellows >> > >>> will >> > >>> share the fix plan here. >> > >>> >> > >>> In the meantime >> > >>> >> > >>> - Artem agreed to help on the docs side: >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top >> banner of >> > >>> Ignite website: https://ignite.apache.org/index.html >> > >>> >> > >>> >> > >>> - >> > >>> Denis >> > >>> >> > >> >> > >> > |
|
|
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 "11.0.2" 2019-01-15 LTS". By some reason, the script fails to set JVM_OPT parameters. If I do "export JVM_OPT={parameters from the doc}" then everything starts working. - Denis On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> wrote: > 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 > < > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > > > > > > 19 suites & 580 tests failed. So we need to do one-by-one research for > occurred problems. > > > > 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. > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs to be > fixed. I hope Peter I. will pick up it, fix is quite simple. > > Details about illegal access and its warning can be found here: > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > > > > 2. Ignition.start warnings: > https://issues.apache.org/jira/browse/IGNITE-11155 > > > > 3. I’ve done some fixes in the > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, and I’m > going to validate results once our Release is passing. Today’s build failed > > > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > > > > Sincerely, > > Dmitriy Pavlov > > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > > > 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 may be just a warning about > > illegal-access, even if it is set =permit. After this warning (it is > > unavoidable for 1st time), everything should be ok. > > > > Sincerely, > > Dmitriy Pavlov > > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > > > >> 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 can be compiled and run with Java 11 > >> 4. Make Ignite buildable with Java 11 > >> > >> Points 1-3 are quick. Dmitriy are you the one who is looking into it? > When > >> can we release Ignite 2.8. We should do this as soon as possible. > >> > >> - > >> Denis > >> > >> > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email]> > >> wrote: > >> > >> > 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 defaults using maven on IntelliJ > >> > settings, please share. > >> > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > >> > > >> > > 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. > >> > > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > >> > > > >> > >> 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 10.0.2 on Windows 10. The only issue was with JAXB > >> > >> dependencies, but it is definitely not related to Apache Ignite. > >> > >> > >> > >> BTW, thank you for the banner. > >> > >> > >> > >> Sincerely, > >> > >> Dmitriy Pavlov > >> > >> > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > >> > >> > >> > >>> 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 (same issue as with > cmd). > >> > As a > >> > >>> committer, I know how to fix it ( > >> > >>> > >> > >>> > >> > > >> > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > >> > >>> ), > >> > >>> but most of the developers have no glue and will give up > >> > >>> - The step above have to be repeated for every single sample > >> > >>> > >> > >>> We briefly discussed this with some community managers and our > >> fellows > >> > >>> will > >> > >>> share the fix plan here. > >> > >>> > >> > >>> In the meantime > >> > >>> > >> > >>> - Artem agreed to help on the docs side: > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top > >> banner of > >> > >>> Ignite website: https://ignite.apache.org/index.html > >> > >>> > >> > >>> > >> > >>> - > >> > >>> Denis > >> > >>> > >> > >> > >> > > >> > > > |
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 standalone-pom. I've added notice into Github MD about it: https://github.com/apache/ignite/tree/master/examples#contributing-to-examples Denis, I will not be able to hunt/recruit individuals to contribute, so 'driving' is better to treat as 'contributing'. About your failure at MAC OS, could you please create a separate issue for this? You can link it with the umbrella. Sincerely, Dmitriy Pavlov пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: > 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 "11.0.2" 2019-01-15 LTS". > > By some reason, the script fails to set JVM_OPT parameters. If I do "export > JVM_OPT={parameters from the doc}" then everything starts working. > > - > Denis > > > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> wrote: > > > 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 > > < > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > > > > > > > > > > > 19 suites & 580 tests failed. So we need to do one-by-one research for > > occurred problems. > > > > > > > > 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. > > > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs to > be > > fixed. I hope Peter I. will pick up it, fix is quite simple. > > > > Details about illegal access and its warning can be found here: > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > > > > > > > > 2. Ignition.start warnings: > > https://issues.apache.org/jira/browse/IGNITE-11155 > > > > > > > > 3. I’ve done some fixes in the > > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, and I’m > > going to validate results once our Release is passing. Today’s build > failed > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > > > > > 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 may be just a warning > about > > > illegal-access, even if it is set =permit. After this warning (it is > > > unavoidable for 1st time), everything should be ok. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > > > > > >> 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 can be compiled and run with Java 11 > > >> 4. Make Ignite buildable with Java 11 > > >> > > >> Points 1-3 are quick. Dmitriy are you the one who is looking into it? > > When > > >> can we release Ignite 2.8. We should do this as soon as possible. > > >> > > >> - > > >> Denis > > >> > > >> > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email]> > > >> wrote: > > >> > > >> > 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 defaults using maven on IntelliJ > > >> > settings, please share. > > >> > > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > > >> > > > >> > > 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. > > >> > > > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email]>: > > >> > > > > >> > >> 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 10.0.2 on Windows 10. The only issue was with JAXB > > >> > >> dependencies, but it is definitely not related to Apache Ignite. > > >> > >> > > >> > >> BTW, thank you for the banner. > > >> > >> > > >> > >> Sincerely, > > >> > >> Dmitriy Pavlov > > >> > >> > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > > >> > >> > > >> > >>> 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 (same issue as with > > cmd). > > >> > As a > > >> > >>> committer, I know how to fix it ( > > >> > >>> > > >> > >>> > > >> > > > >> > > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > > >> > >>> ), > > >> > >>> but most of the developers have no glue and will give up > > >> > >>> - The step above have to be repeated for every single > sample > > >> > >>> > > >> > >>> We briefly discussed this with some community managers and our > > >> fellows > > >> > >>> will > > >> > >>> share the fix plan here. > > >> > >>> > > >> > >>> In the meantime > > >> > >>> > > >> > >>> - Artem agreed to help on the docs side: > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top > > >> banner of > > >> > >>> Ignite website: https://ignite.apache.org/index.html > > >> > >>> > > >> > >>> > > >> > >>> - > > >> > >>> Denis > > >> > >>> > > >> > >> > > >> > > > >> > > > > > > |
|
|
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 <[hidden email]> wrote: > 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 standalone-pom. I've added notice into Github MD about it: > > https://github.com/apache/ignite/tree/master/examples#contributing-to-examples > > Denis, > > I will not be able to hunt/recruit individuals to contribute, so 'driving' > is better to treat as 'contributing'. About your failure at MAC OS, could > you please create a separate issue for this? You can link it with the > umbrella. > > Sincerely, > Dmitriy Pavlov > > пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: > > > 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 "11.0.2" 2019-01-15 LTS". > > > > By some reason, the script fails to set JVM_OPT parameters. If I do > "export > > JVM_OPT={parameters from the doc}" then everything starts working. > > > > - > > Denis > > > > > > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> > wrote: > > > > > 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 > > > < > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > > > > > > > > > > > > > > > > 19 suites & 580 tests failed. So we need to do one-by-one research for > > > occurred problems. > > > > > > > > > > > > 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. > > > > > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs to > > be > > > fixed. I hope Peter I. will pick up it, fix is quite simple. > > > > > > Details about illegal access and its warning can be found here: > > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > > > > > > > > > > > > 2. Ignition.start warnings: > > > https://issues.apache.org/jira/browse/IGNITE-11155 > > > > > > > > > > > > 3. I’ve done some fixes in the > > > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, and > I’m > > > going to validate results once our Release is passing. Today’s build > > failed > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > > > > > > > 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 may be just a warning > > about > > > > illegal-access, even if it is set =permit. After this warning (it is > > > > unavoidable for 1st time), everything should be ok. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > > > > > > > >> 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 can be compiled and run with Java 11 > > > >> 4. Make Ignite buildable with Java 11 > > > >> > > > >> Points 1-3 are quick. Dmitriy are you the one who is looking into > it? > > > When > > > >> can we release Ignite 2.8. We should do this as soon as possible. > > > >> > > > >> - > > > >> Denis > > > >> > > > >> > > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov <[hidden email] > > > > > >> wrote: > > > >> > > > >> > 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 defaults using maven on > IntelliJ > > > >> > settings, please share. > > > >> > > > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email]>: > > > >> > > > > >> > > 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. > > > >> > > > > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov <[hidden email] > >: > > > >> > > > > > >> > >> 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 10.0.2 on Windows 10. The only issue was with > JAXB > > > >> > >> dependencies, but it is definitely not related to Apache > Ignite. > > > >> > >> > > > >> > >> BTW, thank you for the banner. > > > >> > >> > > > >> > >> Sincerely, > > > >> > >> Dmitriy Pavlov > > > >> > >> > > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: > > > >> > >> > > > >> > >>> 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 (same issue as with > > > cmd). > > > >> > As a > > > >> > >>> committer, I know how to fix it ( > > > >> > >>> > > > >> > >>> > > > >> > > > > >> > > > > > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > > > >> > >>> ), > > > >> > >>> but most of the developers have no glue and will give up > > > >> > >>> - The step above have to be repeated for every single > > sample > > > >> > >>> > > > >> > >>> We briefly discussed this with some community managers and our > > > >> fellows > > > >> > >>> will > > > >> > >>> share the fix plan here. > > > >> > >>> > > > >> > >>> In the meantime > > > >> > >>> > > > >> > >>> - Artem agreed to help on the docs side: > > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top > > > >> banner of > > > >> > >>> Ignite website: https://ignite.apache.org/index.html > > > >> > >>> > > > >> > >>> > > > >> > >>> - > > > >> > >>> Denis > > > >> > >>> > > > >> > >> > > > >> > > > > >> > > > > > > > > > > |
|
|
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:23 AM Denis Magda <[hidden email]> wrote: > 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 <[hidden email]> wrote: > >> 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 standalone-pom. I've added notice into Github MD about it: >> >> https://github.com/apache/ignite/tree/master/examples#contributing-to-examples >> >> Denis, >> >> I will not be able to hunt/recruit individuals to contribute, so 'driving' >> is better to treat as 'contributing'. About your failure at MAC OS, could >> you please create a separate issue for this? You can link it with the >> umbrella. >> >> Sincerely, >> Dmitriy Pavlov >> >> пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: >> >> > 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 "11.0.2" 2019-01-15 LTS". >> > >> > By some reason, the script fails to set JVM_OPT parameters. If I do >> "export >> > JVM_OPT={parameters from the doc}" then everything starts working. >> > >> > - >> > Denis >> > >> > >> > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> >> wrote: >> > >> > > 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 >> > > < >> > > >> > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv >> > > > >> > > >> > > >> > > >> > > 19 suites & 580 tests failed. So we need to do one-by-one research for >> > > occurred problems. >> > > >> > > >> > > >> > > 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. >> > > >> > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs >> to >> > be >> > > fixed. I hope Peter I. will pick up it, fix is quite simple. >> > > >> > > Details about illegal access and its warning can be found here: >> > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation >> > > >> > > >> > > >> > > 2. Ignition.start warnings: >> > > https://issues.apache.org/jira/browse/IGNITE-11155 >> > > >> > > >> > > >> > > 3. I’ve done some fixes in the >> > > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, and >> I’m >> > > going to validate results once our Release is passing. Today’s build >> > failed >> > > >> > > >> > > >> > >> https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E >> > > >> > > >> > > >> > > Sincerely, >> > > >> > > Dmitriy Pavlov >> > > >> > > >> > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: >> > > >> > > > 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 may be just a warning >> > about >> > > > illegal-access, even if it is set =permit. After this warning (it is >> > > > unavoidable for 1st time), everything should be ok. >> > > > >> > > > Sincerely, >> > > > Dmitriy Pavlov >> > > > >> > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: >> > > > >> > > >> 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 can be compiled and run with Java 11 >> > > >> 4. Make Ignite buildable with Java 11 >> > > >> >> > > >> Points 1-3 are quick. Dmitriy are you the one who is looking into >> it? >> > > When >> > > >> can we release Ignite 2.8. We should do this as soon as possible. >> > > >> >> > > >> - >> > > >> Denis >> > > >> >> > > >> >> > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov < >> [hidden email]> >> > > >> wrote: >> > > >> >> > > >> > 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 defaults using maven on >> IntelliJ >> > > >> > settings, please share. >> > > >> > >> > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov <[hidden email] >> >: >> > > >> > >> > > >> > > 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. >> > > >> > > >> > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov < >> [hidden email]>: >> > > >> > > >> > > >> > >> 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 10.0.2 on Windows 10. The only issue was with >> JAXB >> > > >> > >> dependencies, but it is definitely not related to Apache >> Ignite. >> > > >> > >> >> > > >> > >> BTW, thank you for the banner. >> > > >> > >> >> > > >> > >> Sincerely, >> > > >> > >> Dmitriy Pavlov >> > > >> > >> >> > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email]>: >> > > >> > >> >> > > >> > >>> 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 (same issue as >> with >> > > cmd). >> > > >> > As a >> > > >> > >>> committer, I know how to fix it ( >> > > >> > >>> >> > > >> > >>> >> > > >> > >> > > >> >> > > >> > >> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 >> > > >> > >>> ), >> > > >> > >>> but most of the developers have no glue and will give >> up >> > > >> > >>> - The step above have to be repeated for every single >> > sample >> > > >> > >>> >> > > >> > >>> We briefly discussed this with some community managers and >> our >> > > >> fellows >> > > >> > >>> will >> > > >> > >>> share the fix plan here. >> > > >> > >>> >> > > >> > >>> In the meantime >> > > >> > >>> >> > > >> > >>> - Artem agreed to help on the docs side: >> > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 >> > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a top >> > > >> banner of >> > > >> > >>> Ignite website: https://ignite.apache.org/index.html >> > > >> > >>> >> > > >> > >>> >> > > >> > >>> - >> > > >> > >>> Denis >> > > >> > >>> >> > > >> > >> >> > > >> > >> > > >> >> > > > >> > > >> > >> > |
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.8. вт, 5 мар. 2019 г. в 07:25, Denis Magda <[hidden email]>: > 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:23 AM Denis Magda <[hidden email]> wrote: > > > 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 <[hidden email]> > wrote: > > > >> 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 standalone-pom. I've added notice into Github MD about > it: > >> > >> > https://github.com/apache/ignite/tree/master/examples#contributing-to-examples > >> > >> Denis, > >> > >> I will not be able to hunt/recruit individuals to contribute, so > 'driving' > >> is better to treat as 'contributing'. About your failure at MAC OS, > could > >> you please create a separate issue for this? You can link it with the > >> umbrella. > >> > >> Sincerely, > >> Dmitriy Pavlov > >> > >> пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: > >> > >> > 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 "11.0.2" 2019-01-15 LTS". > >> > > >> > By some reason, the script fails to set JVM_OPT parameters. If I do > >> "export > >> > JVM_OPT={parameters from the doc}" then everything starts working. > >> > > >> > - > >> > Denis > >> > > >> > > >> > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> > >> wrote: > >> > > >> > > 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 > >> > > < > >> > > > >> > > >> > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > >> > > > > >> > > > >> > > > >> > > > >> > > 19 suites & 580 tests failed. So we need to do one-by-one research > for > >> > > occurred problems. > >> > > > >> > > > >> > > > >> > > 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. > >> > > > >> > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 needs > >> to > >> > be > >> > > fixed. I hope Peter I. will pick up it, fix is quite simple. > >> > > > >> > > Details about illegal access and its warning can be found here: > >> > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > >> > > > >> > > > >> > > > >> > > 2. Ignition.start warnings: > >> > > https://issues.apache.org/jira/browse/IGNITE-11155 > >> > > > >> > > > >> > > > >> > > 3. I’ve done some fixes in the > >> > > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, > and > >> I’m > >> > > going to validate results once our Release is passing. Today’s build > >> > failed > >> > > > >> > > > >> > > > >> > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > >> > > > >> > > > >> > > > >> > > Sincerely, > >> > > > >> > > Dmitriy Pavlov > >> > > > >> > > > >> > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > >> > > > >> > > > 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 may be just a > warning > >> > about > >> > > > illegal-access, even if it is set =permit. After this warning (it > is > >> > > > unavoidable for 1st time), everything should be ok. > >> > > > > >> > > > Sincerely, > >> > > > Dmitriy Pavlov > >> > > > > >> > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > >> > > > > >> > > >> 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 can be compiled and run with Java > 11 > >> > > >> 4. Make Ignite buildable with Java 11 > >> > > >> > >> > > >> Points 1-3 are quick. Dmitriy are you the one who is looking into > >> it? > >> > > When > >> > > >> can we release Ignite 2.8. We should do this as soon as possible. > >> > > >> > >> > > >> - > >> > > >> Denis > >> > > >> > >> > > >> > >> > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov < > >> [hidden email]> > >> > > >> wrote: > >> > > >> > >> > > >> > 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 defaults using maven on > >> IntelliJ > >> > > >> > settings, please share. > >> > > >> > > >> > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov < > [hidden email] > >> >: > >> > > >> > > >> > > >> > > 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. > >> > > >> > > > >> > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov < > >> [hidden email]>: > >> > > >> > > > >> > > >> > >> 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 10.0.2 on Windows 10. The only issue was with > >> JAXB > >> > > >> > >> dependencies, but it is definitely not related to Apache > >> Ignite. > >> > > >> > >> > >> > > >> > >> BTW, thank you for the banner. > >> > > >> > >> > >> > > >> > >> Sincerely, > >> > > >> > >> Dmitriy Pavlov > >> > > >> > >> > >> > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda <[hidden email] > >: > >> > > >> > >> > >> > > >> > >>> 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 (same issue as > >> with > >> > > cmd). > >> > > >> > As a > >> > > >> > >>> committer, I know how to fix it ( > >> > > >> > >>> > >> > > >> > >>> > >> > > >> > > >> > > >> > >> > > > >> > > >> > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > >> > > >> > >>> ), > >> > > >> > >>> but most of the developers have no glue and will give > >> up > >> > > >> > >>> - The step above have to be repeated for every single > >> > sample > >> > > >> > >>> > >> > > >> > >>> We briefly discussed this with some community managers and > >> our > >> > > >> fellows > >> > > >> > >>> will > >> > > >> > >>> share the fix plan here. > >> > > >> > >>> > >> > > >> > >>> In the meantime > >> > > >> > >>> > >> > > >> > >>> - Artem agreed to help on the docs side: > >> > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > >> > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a > top > >> > > >> banner of > >> > > >> > >>> Ignite website: https://ignite.apache.org/index.html > >> > > >> > >>> > >> > > >> > >>> > >> > > >> > >>> - > >> > > >> > >>> Denis > >> > > >> > >>> > >> > > >> > >> > >> > > >> > > >> > > >> > >> > > > > >> > > > >> > > >> > > > |
|
|
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 Pavlov <[hidden email]> wrote: > 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.8. > > вт, 5 мар. 2019 г. в 07:25, Denis Magda <[hidden email]>: > > > 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:23 AM Denis Magda <[hidden email]> wrote: > > > > > 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 <[hidden email]> > > wrote: > > > > > >> 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 standalone-pom. I've added notice into Github MD about > > it: > > >> > > >> > > > https://github.com/apache/ignite/tree/master/examples#contributing-to-examples > > >> > > >> Denis, > > >> > > >> I will not be able to hunt/recruit individuals to contribute, so > > 'driving' > > >> is better to treat as 'contributing'. About your failure at MAC OS, > > could > > >> you please create a separate issue for this? You can link it with the > > >> umbrella. > > >> > > >> Sincerely, > > >> Dmitriy Pavlov > > >> > > >> пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: > > >> > > >> > 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 "11.0.2" 2019-01-15 LTS". > > >> > > > >> > By some reason, the script fails to set JVM_OPT parameters. If I do > > >> "export > > >> > JVM_OPT={parameters from the doc}" then everything starts working. > > >> > > > >> > - > > >> > Denis > > >> > > > >> > > > >> > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email]> > > >> wrote: > > >> > > > >> > > 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 > > >> > > < > > >> > > > > >> > > > >> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > 19 suites & 580 tests failed. So we need to do one-by-one research > > for > > >> > > occurred problems. > > >> > > > > >> > > > > >> > > > > >> > > 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. > > >> > > > > >> > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 > needs > > >> to > > >> > be > > >> > > fixed. I hope Peter I. will pick up it, fix is quite simple. > > >> > > > > >> > > Details about illegal access and its warning can be found here: > > >> > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > > >> > > > > >> > > > > >> > > > > >> > > 2. Ignition.start warnings: > > >> > > https://issues.apache.org/jira/browse/IGNITE-11155 > > >> > > > > >> > > > > >> > > > > >> > > 3. I’ve done some fixes in the > > >> > > https://issues.apache.org/jira/browse/IGNITE-11140 for examples, > > and > > >> I’m > > >> > > going to validate results once our Release is passing. Today’s > build > > >> > failed > > >> > > > > >> > > > > >> > > > > >> > > > >> > > > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > > >> > > > > >> > > > > >> > > > > >> > > Sincerely, > > >> > > > > >> > > Dmitriy Pavlov > > >> > > > > >> > > > > >> > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email]>: > > >> > > > > >> > > > 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 may be just a > > warning > > >> > about > > >> > > > illegal-access, even if it is set =permit. After this warning > (it > > is > > >> > > > unavoidable for 1st time), everything should be ok. > > >> > > > > > >> > > > Sincerely, > > >> > > > Dmitriy Pavlov > > >> > > > > > >> > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > > >> > > > > > >> > > >> 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 can be compiled and run with Java > > 11 > > >> > > >> 4. Make Ignite buildable with Java 11 > > >> > > >> > > >> > > >> Points 1-3 are quick. Dmitriy are you the one who is looking > into > > >> it? > > >> > > When > > >> > > >> can we release Ignite 2.8. We should do this as soon as > possible. > > >> > > >> > > >> > > >> - > > >> > > >> Denis > > >> > > >> > > >> > > >> > > >> > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov < > > >> [hidden email]> > > >> > > >> wrote: > > >> > > >> > > >> > > >> > 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 defaults using maven on > > >> IntelliJ > > >> > > >> > settings, please share. > > >> > > >> > > > >> > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov < > > [hidden email] > > >> >: > > >> > > >> > > > >> > > >> > > 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. > > >> > > >> > > > > >> > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov < > > >> [hidden email]>: > > >> > > >> > > > > >> > > >> > >> 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 10.0.2 on Windows 10. The only issue was > with > > >> JAXB > > >> > > >> > >> dependencies, but it is definitely not related to Apache > > >> Ignite. > > >> > > >> > >> > > >> > > >> > >> BTW, thank you for the banner. > > >> > > >> > >> > > >> > > >> > >> Sincerely, > > >> > > >> > >> Dmitriy Pavlov > > >> > > >> > >> > > >> > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda < > [hidden email] > > >: > > >> > > >> > >> > > >> > > >> > >>> 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 (same issue as > > >> with > > >> > > cmd). > > >> > > >> > As a > > >> > > >> > >>> committer, I know how to fix it ( > > >> > > >> > >>> > > >> > > >> > >>> > > >> > > >> > > > >> > > >> > > >> > > > > >> > > > >> > > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > > >> > > >> > >>> ), > > >> > > >> > >>> but most of the developers have no glue and will > give > > >> up > > >> > > >> > >>> - The step above have to be repeated for every > single > > >> > sample > > >> > > >> > >>> > > >> > > >> > >>> We briefly discussed this with some community managers > and > > >> our > > >> > > >> fellows > > >> > > >> > >>> will > > >> > > >> > >>> share the fix plan here. > > >> > > >> > >>> > > >> > > >> > >>> In the meantime > > >> > > >> > >>> > > >> > > >> > >>> - Artem agreed to help on the docs side: > > >> > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > > >> > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" as a > > top > > >> > > >> banner of > > >> > > >> > >>> Ignite website: https://ignite.apache.org/index.html > > >> > > >> > >>> > > >> > > >> > >>> > > >> > > >> > >>> - > > >> > > >> > >>> Denis > > >> > > >> > >>> > > >> > > >> > >> > > >> > > >> > > > >> > > >> > > >> > > > > > >> > > > > >> > > > >> > > > > > > |
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/IGNITE-11461 We can make some our jars modular without API changes (some will require breaking changes and 3.0). Also, please don't be confused about if we have Java 11 support or not. Provided that we bypass a couple of usability issues, we still don't have Java 9 full support since we don't test code there. Farther from the master state, more problem users will have. вт, 5 мар. 2019 г. в 10:37, Denis Magda <[hidden email]>: > 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 Pavlov <[hidden email]> wrote: > > > 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.8. > > > > вт, 5 мар. 2019 г. в 07:25, Denis Magda <[hidden email]>: > > > > > 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:23 AM Denis Magda <[hidden email]> wrote: > > > > > > > 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 <[hidden email]> > > > wrote: > > > > > > > >> 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 standalone-pom. I've added notice into Github MD > about > > > it: > > > >> > > > >> > > > > > > https://github.com/apache/ignite/tree/master/examples#contributing-to-examples > > > >> > > > >> Denis, > > > >> > > > >> I will not be able to hunt/recruit individuals to contribute, so > > > 'driving' > > > >> is better to treat as 'contributing'. About your failure at MAC OS, > > > could > > > >> you please create a separate issue for this? You can link it with > the > > > >> umbrella. > > > >> > > > >> Sincerely, > > > >> Dmitriy Pavlov > > > >> > > > >> пт, 1 февр. 2019 г. в 22:40, Denis Magda <[hidden email]>: > > > >> > > > >> > 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 "11.0.2" 2019-01-15 LTS". > > > >> > > > > >> > By some reason, the script fails to set JVM_OPT parameters. If I > do > > > >> "export > > > >> > JVM_OPT={parameters from the doc}" then everything starts working. > > > >> > > > > >> > - > > > >> > Denis > > > >> > > > > >> > > > > >> > On Fri, Feb 1, 2019 at 5:53 AM Dmitriy Pavlov <[hidden email] > > > > > >> wrote: > > > >> > > > > >> > > 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 > > > >> > > < > > > >> > > > > > >> > > > > >> > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155&tab=buildTypeStatusDiv > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > 19 suites & 580 tests failed. So we need to do one-by-one > research > > > for > > > >> > > occurred problems. > > > >> > > > > > >> > > > > > >> > > > > > >> > > 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. > > > >> > > > > > >> > > Control.sh https://issues.apache.org/jira/browse/IGNITE-11153 > > needs > > > >> to > > > >> > be > > > >> > > fixed. I hope Peter I. will pick up it, fix is quite simple. > > > >> > > > > > >> > > Details about illegal access and its warning can be found here: > > > >> > > http://openjdk.java.net/jeps/261#Relaxed-strong-encapsulation > > > >> > > > > > >> > > > > > >> > > > > > >> > > 2. Ignition.start warnings: > > > >> > > https://issues.apache.org/jira/browse/IGNITE-11155 > > > >> > > > > > >> > > > > > >> > > > > > >> > > 3. I’ve done some fixes in the > > > >> > > https://issues.apache.org/jira/browse/IGNITE-11140 for > examples, > > > and > > > >> I’m > > > >> > > going to validate results once our Release is passing. Today’s > > build > > > >> > failed > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=2965908&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&branch_Releases_NightlyRelease=%3Cdefault%3E > > > >> > > > > > >> > > > > > >> > > > > > >> > > Sincerely, > > > >> > > > > > >> > > Dmitriy Pavlov > > > >> > > > > > >> > > > > > >> > > пт, 1 февр. 2019 г. в 00:18, Dmitriy Pavlov <[hidden email] > >: > > > >> > > > > > >> > > > 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 may be just a > > > warning > > > >> > about > > > >> > > > illegal-access, even if it is set =permit. After this warning > > (it > > > is > > > >> > > > unavoidable for 1st time), everything should be ok. > > > >> > > > > > > >> > > > Sincerely, > > > >> > > > Dmitriy Pavlov > > > >> > > > > > > >> > > > чт, 31 янв. 2019 г. в 22:38, Denis Magda <[hidden email]>: > > > >> > > > > > > >> > > >> 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 can be compiled and run with > Java > > > 11 > > > >> > > >> 4. Make Ignite buildable with Java 11 > > > >> > > >> > > > >> > > >> Points 1-3 are quick. Dmitriy are you the one who is looking > > into > > > >> it? > > > >> > > When > > > >> > > >> can we release Ignite 2.8. We should do this as soon as > > possible. > > > >> > > >> > > > >> > > >> - > > > >> > > >> Denis > > > >> > > >> > > > >> > > >> > > > >> > > >> On Wed, Jan 30, 2019 at 12:04 PM Dmitriy Pavlov < > > > >> [hidden email]> > > > >> > > >> wrote: > > > >> > > >> > > > >> > > >> > 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 defaults using maven on > > > >> IntelliJ > > > >> > > >> > settings, please share. > > > >> > > >> > > > > >> > > >> > ср, 30 янв. 2019 г. в 14:56, Dmitriy Pavlov < > > > [hidden email] > > > >> >: > > > >> > > >> > > > > >> > > >> > > 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. > > > >> > > >> > > > > > >> > > >> > > вт, 29 янв. 2019 г. в 18:04, Dmitriy Pavlov < > > > >> [hidden email]>: > > > >> > > >> > > > > > >> > > >> > >> 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 10.0.2 on Windows 10. The only issue was > > with > > > >> JAXB > > > >> > > >> > >> dependencies, but it is definitely not related to Apache > > > >> Ignite. > > > >> > > >> > >> > > > >> > > >> > >> BTW, thank you for the banner. > > > >> > > >> > >> > > > >> > > >> > >> Sincerely, > > > >> > > >> > >> Dmitriy Pavlov > > > >> > > >> > >> > > > >> > > >> > >> пн, 28 янв. 2019 г. в 23:30, Denis Magda < > > [hidden email] > > > >: > > > >> > > >> > >> > > > >> > > >> > >>> 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 (same issue > as > > > >> with > > > >> > > cmd). > > > >> > > >> > As a > > > >> > > >> > >>> committer, I know how to fix it ( > > > >> > > >> > >>> > > > >> > > >> > >>> > > > >> > > >> > > > > >> > > >> > > > >> > > > > > >> > > > > >> > > > > > > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > > > >> > > >> > >>> ), > > > >> > > >> > >>> but most of the developers have no glue and will > > give > > > >> up > > > >> > > >> > >>> - The step above have to be repeated for every > > single > > > >> > sample > > > >> > > >> > >>> > > > >> > > >> > >>> We briefly discussed this with some community managers > > and > > > >> our > > > >> > > >> fellows > > > >> > > >> > >>> will > > > >> > > >> > >>> share the fix plan here. > > > >> > > >> > >>> > > > >> > > >> > >>> In the meantime > > > >> > > >> > >>> > > > >> > > >> > >>> - Artem agreed to help on the docs side: > > > >> > > >> > >>> https://issues.apache.org/jira/browse/IGNITE-11113 > > > >> > > >> > >>> - I've added "How to Use Ignite on JDK 9, 10, 11" > as a > > > top > > > >> > > >> banner of > > > >> > > >> > >>> Ignite website: > https://ignite.apache.org/index.html > > > >> > > >> > >>> > > > >> > > >> > >>> > > > >> > > >> > >>> - > > > >> > > >> > >>> Denis > > > >> > > >> > >>> > > > >> > > >> > >> > > > >> > > >> > > > > >> > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > > > > > |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |