Re: [PROPOSAL] Move Ignite 2.x to JDK11 compilation

[Peter Ivanov]

Hi, Maksim.

As far as I know - TeamCity is fully prepared for transfer.
It will take a couple of hours (with tests) to move to JDK11 as default and
remove possible JDK8 leftovers.

пт, 12 июл. 2024 г. в 13:26, Maksim Timonin :

> Hi, Igniters!
>
> I suggest it's time to return to the discussion. There were 2 issues that
> blocked the sources moving from jdk1.8 to jdk11 [1, 2] and they have now
> been resolved. I have prepared a patch that changes maven.source.version to
> 11 and it passes MTCGA without blockers [3]. TeamCity already runs RunAll
> every night under jdk11 [4], so changing the default java version should
> not break anything.
>
> I believe it's time we can make the move. The plan is as follows:
>
> 1. Conduct a vote "Move Ignite 2 sources to JDK11".
> 2. Upgrade all TeamCity jobs from jdk1.8 to jdk11.
> 3. Review and merge the patch [3] that changes `maven.source.version` in
> Ignite's pom.xml to 11. This means that Apache Ignite 2.17 will be built
> using jdk11.
> 4. Clean up all code that relies on jdk1.8.
>
> Let's discuss this again. Peter, is there anything that needs to be done on
> TeamCity before the upgrade?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13202
> [2] https://issues.apache.org/jira/browse/IGNITE-22671
> [3] https://issues.apache.org/jira/browse/IGNITE-22669
> [4]
>
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll?mode=builds&tag=JDK_11
>
> On Wed, Oct 25, 2023 at 4:15 AM Николай Ижиков 
> wrote:
>
> > +1
> >
> > > 24 окт. 2023 г., в 19:25, Anton Vinogradov  написал(а):
> > >
> > > ++1 for switch to the OpenJDK framework
> > >
> > > As to original question, I propose to (step-by-step):
> > > 1) Switch to java 11 testing instead of 8
> > > 2) Fix java 11 release
> > > 3) Switch to maven.compiler.source 11 (Vote required)
> > >
> > > On Tue, Oct 24, 2023 at 7:12 PM Dmitriy Pavlov 
> > wrote:
> > >
> > >> ++1 for testing using JDK11
> > >>
> > >> +0 for switching off support of JDK8 runtimes and class version
> (unless
> > >> compilation using JDK11 is done with -target=1.8 our users won't be
> > able to
> > >> run Ignite using Java 8).
> > >>
> > >> I suggest the following next steps: once tests are completely fine on
> > >> Teamcity using JDK 11, we start a separate thread named like:
> > >> "[VOTE] discontinuing JDK 8 since the 2.16 release"
> > >> to make the issue for end users more obvious. Since Nikita volunteers
> > to be
> > >> a Release Manager, I suppose that 2.16 will be released quite soon.
> > >>
> > >> I personally prefer to switch to newer Java. Using newer runtime helps
> > us
> > >> to provide speed and scale, since JVM is developed all the time. But I
> > >> might be unaware of the risks, so let's discuss it later with the
> entire
> > >> dev community.
> > >>
> > >> Sincerely,
> > >> Dmitriy Pavlov
> > >>
> > >> ср, 30 авг. 2023 г. в 19:09, Ivan Daschinsky :
> > >>
> > >>> +1, sounds reasonable for the open source project. IMHO, Eclipse
> > Temurin
> > >>> JDK is a rule of thumb choice nowadays.
> > >>>
> > >>> ср, 30 авг. 2023 г. в 18:40, Peter Ivanov :
> > >>>
> > >>>> Hi, Igniters!
> > >>>>
> > >>>> As part of this proposal I would also like to discuss the JDK
> vendors
> > >> we
> > >>>> are using on our CI platforms TeamCIty.
> > >>>> Historically, Ignite 2.x is being built under Oracle's edition -
> > mostly
> > >>>> because of some features like JFR or similar.
> > >>>> However today we have pretty much solid alternative represented by
> > >>> OpenJDK
> > >>>> and its most popular build Eclipse Temurin, which provides every
> > >> required
> > >>>> version for our needs (and especially LTS versions 1.8, 11 and 17)
> > with
> > >>> all
> > >>>> necessary updates.
> > >>>>
> > >>>> So, I suggest we update our build agents for TeamCity accordingly,
> > >>> provide
> > >>>> OpenJDK framework for those 3 major versions and discontinue
> Oracle's
> > >>>> builds.
> > >>>> WDYT?
> > >>>>
> > >>>

Re: [PROPOSAL] Move Ignite 2.x to JDK11 compilation

[Peter Ivanov]

Hi, Igniters!

As part of this proposal I would also like to discuss the JDK vendors we
are using on our CI platforms TeamCIty.
Historically, Ignite 2.x is being built under Oracle's edition - mostly
because of some features like JFR or similar.
However today we have pretty much solid alternative represented by OpenJDK
and its most popular build Eclipse Temurin, which provides every required
version for our needs (and especially LTS versions 1.8, 11 and 17) with all
necessary updates.

So, I suggest we update our build agents for TeamCity accordingly, provide
OpenJDK framework for those 3 major versions and discontinue Oracle's
builds.
WDYT?

пт, 25 авг. 2023 г. в 12:13, Ivan Daschinsky :

> +1. It's time to do it at last.
>
> пт, 25 авг. 2023 г. в 12:06, Peter Ivanov :
>
> > Mostly, yes.
> >
> > In other words - proposal is about starting shipping Apache Ignite
> releases
> > with JDK11 compiled binaries thus dropping JDK8-10 runtime support.
> >
> > пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :
> >
> > > I looks like you're proposing not migration to 2.11 (because it is
> > already
> > > supported), but Java 8-9 support dropping.
> > >
> > > On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov 
> > wrote:
> > >
> > > > Hi, Igniters!
> > > >
> > > >
> > > > I would like to propose the next, if you don't mind me saying,
> > > > revolutionary step forward in our project: moving Ignite 2.x
> > compilation
> > > to
> > > > JDK11 minimum version.
> > > > I'd rather not make arguments, pros and cons other that currently
> exist
> > > in
> > > > Java world - you know them better than me. Let's just say that it
> seems
> > > > that time has come - consider at least that JDK11 as the LTS version
> is
> > > > already about 4 and a half years on the go, and Ignite 3.x started
> from
> > > > JDK11 right away.
> > > >
> > > > This change may possibly require from us additional efforts on
> > supporting
> > > > the last version with JDK8 in terms of releasing additional patches
> and
> > > > hotfixes a bit longer than usual. However, this is up to the
> community
> > to
> > > > decide.
> > > >
> > > > Currently, Apache Ignite 2.x (with Extensions as well) is already
> > > prepared
> > > > for being compiled with JDK11 and almost all tests are passing. If we
> > > come
> > > > to an agreement about this proposal and designate the next version
> that
> > > > will become the first to provide JDK11 compiled binaries - I am ready
> > to
> > > > start the process of updating the TeamCity building project
> > accordingly.
> > > >
> > > >
> > > > Please, share your thoughts.
> > > >
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: [PROPOSAL] Move Ignite 2.x to JDK11 compilation

[Peter Ivanov]

Mostly, yes.

In other words - proposal is about starting shipping Apache Ignite releases
with JDK11 compiled binaries thus dropping JDK8-10 runtime support.

пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :

> I looks like you're proposing not migration to 2.11 (because it is already
> supported), but Java 8-9 support dropping.
>
> On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov  wrote:
>
> > Hi, Igniters!
> >
> >
> > I would like to propose the next, if you don't mind me saying,
> > revolutionary step forward in our project: moving Ignite 2.x compilation
> to
> > JDK11 minimum version.
> > I'd rather not make arguments, pros and cons other that currently exist
> in
> > Java world - you know them better than me. Let's just say that it seems
> > that time has come - consider at least that JDK11 as the LTS version is
> > already about 4 and a half years on the go, and Ignite 3.x started from
> > JDK11 right away.
> >
> > This change may possibly require from us additional efforts on supporting
> > the last version with JDK8 in terms of releasing additional patches and
> > hotfixes a bit longer than usual. However, this is up to the community to
> > decide.
> >
> > Currently, Apache Ignite 2.x (with Extensions as well) is already
> prepared
> > for being compiled with JDK11 and almost all tests are passing. If we
> come
> > to an agreement about this proposal and designate the next version that
> > will become the first to provide JDK11 compiled binaries - I am ready to
> > start the process of updating the TeamCity building project accordingly.
> >
> >
> > Please, share your thoughts.
> >
>

Re: [ANNOUNCE] Welcome Aleksandr Polovtsev as a new committer

[Peter Ivanov]

Congratulations, keep it going!

пн, 21 авг. 2023 г. в 12:39, Aleksandr Polovtsev :

> Thank you, dear Igniters!
>
> On Mon, Aug 21, 2023 at 10:04 AM Вячеслав Коптилин <
> slava.kopti...@gmail.com>
> wrote:
>
> > Congratulations, Alexander! Keep it up!
> >
> > Thanks,
> > S.
> >
> > пн, 21 авг. 2023 г. в 09:14, Roman Puchkovskiy <
> > roman.puchkovs...@gmail.com
> > >:
> >
> > > Congratulations!
> > >
> > > пн, 21 авг. 2023 г. в 09:29, Pavel Tupitsyn :
> > > >
> > > > Congratulations, Aleksandr! Well deserved!
> > > >
> > > > On Mon, Aug 21, 2023 at 8:01 AM Kseniya Romanova <
> > ksroman...@apache.org>
> > > > wrote:
> > > >
> > > > > Igniters!
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Ignite has
> invited
> > > > > Aleksandr
> > > > > Polovtsev to become a committer and we are pleased to announce that
> > he
> > > has
> > > > > accepted.
> > > > >
> > > > > Alexandr makes valuable contributions to the Apache Ignite code
> > > (including
> > > > > Node Join Protocol and Initialization[1] for the Ignite 3),
> > > participates in
> > > > > important dev discussions and contributes as well to the Project
> > > awareness
> > > > > by presenting twice at the Ignite Summit[2]
> > > > >
> > > > > Please join me in welcoming Alexandr, and congratulating him on the
> > new
> > > > > role in the Apache Ignite Community!
> > > > >
> > > > >
> > > > > Kseniya Romanova
> > > > >
> > > > > on behalf of Apache Ignite PMC
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-77%3A+Node+Join+Protocol+and+Initialization+for+Ignite+3
> > > > >
> > > > >
> > > > > [2] https://ignite-summit.org/2023-june/sessions/484805
> > > > > https://ignite-summit.org/2022-june/sessions/337234
> > > > >
> > >
> >
>
>
> --
> With regards,
> Aleksandr Polovtsev
>

[PROPOSAL] Move Ignite 2.x to JDK11 compilation

[Peter Ivanov]

Hi, Igniters!


I would like to propose the next, if you don't mind me saying,
revolutionary step forward in our project: moving Ignite 2.x compilation to
JDK11 minimum version.
I'd rather not make arguments, pros and cons other that currently exist in
Java world - you know them better than me. Let's just say that it seems
that time has come - consider at least that JDK11 as the LTS version is
already about 4 and a half years on the go, and Ignite 3.x started from
JDK11 right away.

This change may possibly require from us additional efforts on supporting
the last version with JDK8 in terms of releasing additional patches and
hotfixes a bit longer than usual. However, this is up to the community to
decide.

Currently, Apache Ignite 2.x (with Extensions as well) is already prepared
for being compiled with JDK11 and almost all tests are passing. If we come
to an agreement about this proposal and designate the next version that
will become the first to provide JDK11 compiled binaries - I am ready to
start the process of updating the TeamCity building project accordingly.


Please, share your thoughts.

Re: Force push to apache/ignite@master

[Peter Ivanov]

Thanks, Maksim.

Anyway, I suggest to notify community just about such cases for better
transparency.

чт, 16 мар. 2023 г. в 12:52, Maksim Timonin :

> Hi, Peter!
>
> Yes, I've pushed to the master branch. Actually it was a fix of the commit
> message. There was about 1 min difference between original commit and the
> fix.
>
> I checked master before the fix, and actually it happened at night. Usually
> no commits are performed this time.
>
> Sorry, for doing that :( it was an exceptional case.
>
> чт, 16 мар. 2023 г., 10:18 Peter Ivanov :
>
> > Hi, Igniters!
> >
> > Recently I've noticed that somehow the history of the *master* branch of
> > apache/ignite project has been changed.
> > The changed commit is the following:
> > *Thu Mar 9 22:52:10 2023 +0300 : Thu Mar 9 22:59:03 2023 +0300 a8e1689951
> > (2023-03-09 22:59:03 +0300) Maksim Timonin  > > IGNITE-17177 Added incremental snapshots
> > (#10539)*
> > Previous hash was 04304d4e9e
> >
> > As it seems, someone (supposedly Maksim himself) updated the master
> branch
> > with forced history rewriting.
> >
> > So the questions are:
> > 1. Why? Was there a serious reason to do so, breaking all processes
> > connected to master branch update?
> > 2. How? Do we not have limitations for master branch rewriting?
> >
>

Force push to apache/ignite@master

[Peter Ivanov]

Hi, Igniters!

Recently I've noticed that somehow the history of the *master* branch of
apache/ignite project has been changed.
The changed commit is the following:
*Thu Mar 9 22:52:10 2023 +0300 : Thu Mar 9 22:59:03 2023 +0300 a8e1689951
(2023-03-09 22:59:03 +0300) Maksim Timonin > IGNITE-17177 Added incremental snapshots
(#10539)*
Previous hash was 04304d4e9e

As it seems, someone (supposedly Maksim himself) updated the master branch
with forced history rewriting.

So the questions are:
1. Why? Was there a serious reason to do so, breaking all processes
connected to master branch update?
2. How? Do we not have limitations for master branch rewriting?

[jira] [Created] (IGNITE-14132) Add configuration to separate Integration and Unit tests

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-14132:
-

 Summary: Add configuration to separate Integration and Unit tests
 Key: IGNITE-14132
 URL: https://issues.apache.org/jira/browse/IGNITE-14132
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov


After IGNITE-14123, Unit and Integration tests are separated.

However, Maven goal {{integration-test}} includes unit tests too.

There is an option to add external property to skip unit tests only which 
should be added to {{parent/pom.xml}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14124) Fix project's Maven settings

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-14124:
-

 Summary: Fix project's Maven settings
 Key: IGNITE-14124
 URL: https://issues.apache.org/jira/browse/IGNITE-14124
 Project: Ignite
  Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 3.0.0-alpha2


https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_RunSanityCheck/5855660?buildTab=dependencies&mode=list



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14061) extdata modules are incorrectly published

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-14061:
-

 Summary: extdata modules are incorrectly published
 Key: IGNITE-14061
 URL: https://issues.apache.org/jira/browse/IGNITE-14061
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov


ignite-extdata* modules are used in tests but it turns out that they're also 
being deployed to Maven.

Need to skipped deployment for these modules.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14016) Prepare an RPM package for Ignite 3.0

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-14016:
-

 Summary: Prepare an RPM package for Ignite 3.0
 Key: IGNITE-14016
 URL: https://issues.apache.org/jira/browse/IGNITE-14016
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14011) Add RAT&headers check, PMD, Idea Inspections, and code style suites for Ignite 3 project

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-14011:
-

 Summary: Add RAT&headers check, PMD, Idea Inspections, and code 
style suites for Ignite 3 project
 Key: IGNITE-14011
 URL: https://issues.apache.org/jira/browse/IGNITE-14011
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


We need to copy the following suites to Ignite 3 (public TC). Please create a 
corresponding ticket in Ignite JIRA if pom.xml modifications are 
required.https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?mode=builds#all-projectshttps://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_InspectionsCore?mode=builds#all-projects
 (assuming TC will be able to run inspections check on the new 
repository)https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projectshttps://ggtc.gridgain.com/buildConfiguration/Tests_GridGainCeEeUe_Latest_SanityCheck_Pmd?mode=builds



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13319) Docker: trim whitespaces in the OPTION_LIBS parameter

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-13319:
-

 Summary: Docker: trim whitespaces in the OPTION_LIBS parameter
 Key: IGNITE-13319
 URL: https://issues.apache.org/jira/browse/IGNITE-13319
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov


When you list several libraries in the OPTION_LIB parameter, you have to follow 
this format “ignite-aws,ignite-camel” with no whitespaces between the names.

If anybody puts a space before the ignite-camel like this “ignite-aws, 
ignite-camel” then the second library won’t be added to the classpath.

We need to trim all the whitespaces in the OPTION_LIB before passing the libs 
to the launch script.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12173) Fix http links

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-12173:
-

 Summary: Fix http links
 Key: IGNITE-12173
 URL: https://issues.apache.org/jira/browse/IGNITE-12173
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.7.5
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


h3. [Apache Ignite|https://github.com/apache]
# 
{{[http://h2database.com/m2-repo|https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L233]}}
# 
{{[http://hadoop.apache.org/docs/current/api/|https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L339]}}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (IGNITE-12160) Fix RPM packages build

[Peter Ivanov (Jira)]

Peter Ivanov created IGNITE-12160:
-

 Summary: Fix RPM packages build
 Key: IGNITE-12160
 URL: https://issues.apache.org/jira/browse/IGNITE-12160
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


{{Tue 10 Sep 2019 Peter Ivanov  - 2.7.6-1}} date is in 
invalid format and should be fixed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (IGNITE-11751) Javadoc broken

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-11751:
-

 Summary: Javadoc broken
 Key: IGNITE-11751
 URL: https://issues.apache.org/jira/browse/IGNITE-11751
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
 Fix For: 2.8


{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:aggregate (core-javadoc) on 
project apache-ignite: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - 
ignite/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/serializer/package-info.java:21:
 warning: a package-info.java file has already been seen for package 
org.apache.ignite.cache.store.cassandra.serializer
[ERROR] package org.apache.ignite.cache.store.cassandra.serializer;
[ERROR]^
[ERROR] javadoc: warning - Multiple sources of package comments found for 
package "org.apache.ignite.cache.store.cassandra.serializer"
[ERROR] javadoc: error - Error - Exception java.lang.ClassNotFoundException 
thrown while trying to register Taglet 
org.apache.ignite.tools.javadoc.IgniteLinkTaglet...
[ERROR] ignite/modules/core/src/main/java/org/apache/ignite/Ignition.java:88: 
warning - @ignitelink is an unknown tag.
[ERROR] ignite/modules/core/src/main/java/org/apache/ignite/Ignition.java:88: 
warning - @ignitelink is an unknown tag.
[ERROR] ignite/modules/core/src/main/java/org/apache/ignite/Ignition.java:88: 
warning - @ignitelink is an unknown tag.
[ERROR] ignite/modules/core/src/main/java/org/apache/ignite/Ignition.java:88: 
warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java:828:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java:828:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStore.java:71:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStore.java:71:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStoreSessionListener.java:114:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStoreSessionListener.java:114:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStoreSessionListener.java:114:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStoreSessionListener.java:114:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java:120:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/transactions/Transaction.java:120:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/checkpoint/CheckpointSpi.java:60:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/checkpoint/CheckpointSpi.java:60:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.java:233:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.java:233:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/deployment/DeploymentSpi.java:61:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/spi/deployment/DeploymentSpi.java:61:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java:154:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java:154:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java:152:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java:152:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/spring/src/main/java/org/apache/ignite/cache/spring/SpringCacheManager.java:145:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/spring/src/main/java/org/apache/ignite/cache/spring/SpringCacheManager.java:145:
 warning - @ignitelink is an unknown tag.
[ERROR] 
ignite/modules/spring/src/main/java/org/apache/ignite/transactions/spring/SpringTransactionMa

[jira] [Created] (IGNITE-11737) Apache Ignite 2.7.5 Linux packages version update

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-11737:
-

 Summary: Apache Ignite 2.7.5 Linux packages version update
 Key: IGNITE-11737
 URL: https://issues.apache.org/jira/browse/IGNITE-11737
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Update DEB and RPM packages' versions in Apache Ignite for the next version 
(2.7.5)




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-11595) Fix broken Javadoc stylesheet

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-11595:
-

 Summary: Fix broken Javadoc stylesheet
 Key: IGNITE-11595
 URL: https://issues.apache.org/jira/browse/IGNITE-11595
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.7
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.7.5






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10696) Java 9/10/11 Support [2.8]

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10696:
-

 Summary: Java 9/10/11 Support [2.8]
 Key: IGNITE-10696
 URL: https://issues.apache.org/jira/browse/IGNITE-10696
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


Enhance [Ignite Tests 2.4+ (Java 
8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview]
 project with ability to run build and tests under JDK9. Fix all incoming 
problems so that full Run All test runs on same branches provide similar 
results (excluding flaky tests).

Some known problems:
* some current versions of used maven plugins and 3rd party dependencies are 
still not ready for Java 9
* some JVM options of current test build configurations require revision
* scala -- both 2.10 and 2.11 currently used in building and testing do not 
support Java 9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10683) Prepare process of packaging and delivering thin clients

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10683:
-

 Summary: Prepare process of packaging and delivering thin clients
 Key: IGNITE-10683
 URL: https://issues.apache.org/jira/browse/IGNITE-10683
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


# **NodeJs client**
#* +Instruction+: 
https://github.com/nobitlost/ignite/blob/ignite--docs/modules/platforms/nodejs/README.md#publish-ignite-nodejs-client-on-npmjscom-instruction
#* +Uploaded+: https://www.npmjs.com/package/apache-ignite-client
# **PHP client**
#* +Instruction+: 
https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md#release-the-client-in-the-php-package-repository-instruction
{panel}
Cannot be uploaded on Packagist as the client should be in a dedicated 
repository for that - 
https://issues.apache.org/jira/browse/IGNITE-7783?focusedCommentId=16595476&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16595476
Installation from the sources works.
{panel}
# **Python client**
I have already registered the package `pyignite` on PyPI[1]. The person who is 
going to take the responsibility of maintaining it should create an account on 
PyPI and mail me in private, so that I can grant them the necessary rights. 
They also must install twine[3].
The process of packaging is well described in the packaging tutorial[2]. In the 
nutshell, the maintainer must do the following:
## Clone/pull the sources from the git repository,
## Enter the directory in which the `setup.py` is resides (“the setup 
directory”), in our case it is `modules/platforms/python`.
## Create the packages with the command `python3 setup.py sdist bdist_wheel`. 
The packages will be created in `modules/platforms/python/dist` folder.
## Upload packages with twine: `twine upload dist/*`.

It is very useful to have a dedicated Python virtual environment prepared to 
perform steps 3-4. Just do an editable install of `pyignite` into that 
environment from the setup directory: `pip3 install -e .` You can also install 
twine (`pip install twine`) in it.

Consider also making a `.pypirc` file to save time on logging in to PyPI. 
Newest version of `twine` is said to support keyrings on Linux and Mac, but I 
have not tried this yet.
[1] https://pypi.org/project/pyignite/
[2] https://packaging.python.org/tutorials/packaging-projects/
[3] https://twine.readthedocs.io/en/latest/
Some other notes on PyPI and versioning.
- The package version is located in the `setup.py`, it is a `version` argument 
of the `setuptools.setup()` function. Editing the `setup.py` is the only way to 
set the package version.
- You absolutely can not replace a package in PyPI (hijacking prevention). If 
you have published the package by mistake, all you can do is delete the 
unwanted package, increment the version counter in `setup.py`, and try again.
- If you upload the package through the web interface of PyPI (without twine), 
the package description will be garbled. Web interface does not support 
markdown.
Anyway, I would like to join in the congratulations on successful release. 
Kudos to the team.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSSION] Relocation of Apache git repositories from git-wip-us.apache.org to GitBox

[Peter Ivanov]

There will be no problem with TC, as we use GitHub as main VCS root, using ASF 
only for release (which I will reconfigure during release builds refactoring 
and optimisations for AI 2.8).


> On 11 Dec 2018, at 19:25, Alexey Goncharuk  wrote:
> 
> Given that there is no option to stay on the old repository and 
> mass-migration is scheduled for Feb, 7th, I think it is better to prepare and 
> move the repository before the date. 
> 
> As far as I understand, from developers standpoint we only need to change the 
> git remote entry. Petr, Sergey, can you asses what changes are need to be 
> done in order to support this migration for TC and release procedure?
> 
> вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov  >:
> Hi All,
> 
> The Apache Ignite still has a repository on git-wip-us for its code, as
> well, for release.
> 
> Does anyone have a problem with moving over the Ignite git-wip-us
> repository to gitbox voluntarily? This means integrated access and easy PRs
> (write access to the GitHub repo).
> 
> We need to document support for the decision from a mailing list post, so
> here it is.
> 
> Sincerely,
> Dmitriy Pavlov
> 
> сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov  >:
> 
> > Hi Igniters,
> >
> > What do you think about the voluntary migration of project repositories
> > from git-wip to GitBox? (See details in the forwarded email.)
> >
> > Redirection of emails originated by PR actions to notifications@ seems to
> > be almost finished, so email flood issue seems to be already solved for dev@
> > .
> >
> > It is up to us to decide if we would like to migrate sooner. Later all
> > repositories will be migrated anyway.
> >
> > Affected repositories
> > - Ignite Release
> > - Ignite
> >
> > Please share your opinion.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > -- Forwarded message -
> > From: Daniel Gruno mailto:humbed...@apache.org>>
> > Date: пт, 7 дек. 2018 г. в 19:52
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org 
> > To: us...@infra.apache.org  
> > mailto:us...@infra.apache.org>>
> >
> >
> > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
> >   DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
> >
> > Hello Apache projects,
> >
> > I am writing to you because you may have git repositories on the
> > git-wip-us server, which is slated to be decommissioned in the coming
> > months. All repositories will be moved to the new gitbox service which
> > includes direct write access on github as well as the standard ASF
> > commit access via gitbox.apache.org .
> >
> > ## Why this move? ##
> > The move comes as a result of retiring the git-wip service, as the
> > hardware it runs on is longing for retirement. In lieu of this, we
> > have decided to consolidate the two services (git-wip and gitbox), to
> > ease the management of our repository systems and future-proof the
> > underlying hardware. The move is fully automated, and ideally, nothing
> > will change in your workflow other than added features and access to
> > GitHub.
> >
> > ## Timeframe for relocation ##
> > Initially, we are asking that projects voluntarily request to move
> > their repositories to gitbox, hence this email. The voluntary
> > timeframe is between now and January 9th 2019, during which projects
> > are free to either move over to gitbox or stay put on git-wip. After
> > this phase, we will be requiring the remaining projects to move within
> > one month, after which we will move the remaining projects over.
> >
> > To have your project moved in this initial phase, you will need:
> >
> > - Consensus in the project (documented via the mailing list)
> > - File a JIRA ticket with INFRA to voluntarily move your project repos
> >over to gitbox (as stated, this is highly automated and will take
> >between a minute and an hour, depending on the size and number of
> >your repositories)
> >
> > To sum up the preliminary timeline;
> >
> > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
> >relocation
> > - January 9th -> February 6th: Mandated (coordinated) relocation
> > - February 7th: All remaining repositories are mass migrated.
> >
> > This timeline may change to accommodate various scenarios.
> >
> > ## Using GitHub with ASF repositories ##
> > When your project has moved, you are free to use either the ASF
> > repository system (gitbox.apache.org ) OR GitHub 
> > for your development
> > and code pushes. To be able to use GitHub, please follow the primer
> > at: https://reference.apache.org/committer/github 
> > 
> >
> >
> > We appreciate your understanding of this issue, and hope that your
> > project can coordinate voluntarily moving your repositories in a
> > timely manner.
> >
> > A

[jira] [Created] (IGNITE-10675) Refactor Release Candidate check build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10675:
-

 Summary: Refactor Release Candidate check build
 Key: IGNITE-10675
 URL: https://issues.apache.org/jira/browse/IGNITE-10675
 Project: Ignite
  Issue Type: Sub-task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# Revise build, ASC, SHA512, etc. steps.
# Add check for tasks in Jira: all tasks for current RC should be resolved.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10673) Prepare instructions for ASC and SHA512 verification

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10673:
-

 Summary: Prepare instructions for ASC and SHA512 verification
 Key: IGNITE-10673
 URL: https://issues.apache.org/jira/browse/IGNITE-10673
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Prepare instructions for ASC and SHA512 verification



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10600) Revise Apache Ignite release build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10600:
-

 Summary: Revise Apache Ignite release build
 Key: IGNITE-10600
 URL: https://issues.apache.org/jira/browse/IGNITE-10600
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


Current set of Apache Ignite release builds on TC have to be revised and 
refactored to become more stable and understandable.
Also, release documentation has to be modified to fit the changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10596) Introduce Docker images release build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10596:
-

 Summary: Introduce Docker images release build
 Key: IGNITE-10596
 URL: https://issues.apache.org/jira/browse/IGNITE-10596
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


Add new build in [Apache Ignite 
Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8&tab=projectOverview]
 project for building and uploading Docker images based on Release build 
artifacts.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10595) Introduce RPM / DEB Release build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10595:
-

 Summary: Introduce RPM / DEB Release build
 Key: IGNITE-10595
 URL: https://issues.apache.org/jira/browse/IGNITE-10595
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


Add new build in [Apache Ignite 
Release|https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8&tab=projectOverview]
 project for building and uploading RPM / DEB packages based on Release build 
artifacts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10122) Move Web-Console Frontend/Backend Docker images build to dedicated directory

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-10122:
-

 Summary: Move Web-Console Frontend/Backend Docker images build to 
dedicated directory
 Key: IGNITE-10122
 URL: https://issues.apache.org/jira/browse/IGNITE-10122
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Ilya Murchenko
 Fix For: 2.8


It is required to move [frontend / 
backend|https://github.com/apache/ignite/tree/master/modules/web-console/docker/compose]
 Docker build of Web-Console to dedicated directory: {{/docker/compose/}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9974) Drop Hadoop assemblies

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9974:


 Summary: Drop Hadoop assemblies
 Key: IGNITE-9974
 URL: https://issues.apache.org/jira/browse/IGNITE-9974
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.7
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


After dropping Hadoop binaries from release delivery (see IGNITE-9953) it is 
required to drop assemblies and corresponding files / profiles if exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9912) Improve Javadoc suite

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9912:


 Summary: Improve Javadoc suite
 Key: IGNITE-9912
 URL: https://issues.apache.org/jira/browse/IGNITE-9912
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# Add {{javadoc}} profile to maven execution
# Devise a solution to workaround warning about Hibernate duplicate 
package-info (due to Hibernate 4 and 5 modules together in single reactor)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9866) Unify and optimise *.sh and *.bat code base

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9866:


 Summary: Unify and optimise *.sh and *.bat code base
 Key: IGNITE-9866
 URL: https://issues.apache.org/jira/browse/IGNITE-9866
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.7
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.8


There are lots of duplicated code at /bin/*.[sh|bat] scripts (especially -- 
Java run string construction). It is required to move duplicated code to common 
function script.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9865) Javadoc failure on TDE

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9865:


 Summary: Javadoc failure on TDE
 Key: IGNITE-9865
 URL: https://issues.apache.org/jira/browse/IGNITE-9865
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Nikolay Izhikov


After IGNITE-8485 there is Javadoc failure running {{mvn initialise -Pjavadoc}}:
{code}
[10:44:52]  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run 
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException 
has occured: Execution failed due to: 'Other Packages' section should not be 
present, all packages should have corresponding documentation groups: 
/data/teamcity/work/9198da4c51c3e112/target/javadoc/core/overview-summary.html;Please
 add packages description to parent/pom.xml into (maven-javadoc-plugin) 
/  / 
[10:44:52]  [ERROR] 
[10:44:52]  [ERROR] around Ant part .. @ 11:51 in 
/data/teamcity/work/9198da4c51c3e112/target/antrun/build-main.xml
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9772) Remove term "fabric" from Apache Ignite project completely

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9772:


 Summary: Remove term "fabric" from Apache Ignite project completely
 Key: IGNITE-9772
 URL: https://issues.apache.org/jira/browse/IGNITE-9772
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Some files (code, readmes, etc.) still have reference to "fabric" term. It is 
required to eliminate it completely.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9656) Automate RPM and DEB packages version increase on release

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9656:


 Summary: Automate RPM and DEB packages version increase on release
 Key: IGNITE-9656
 URL: https://issues.apache.org/jira/browse/IGNITE-9656
 Project: Ignite
  Issue Type: Task
 Environment: RPM and DEB packages version increase after release 
should be automated and done in the same commit as pom.xml version are 
increased.
Reporter: Peter Ivanov






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9628) Java 9: ML module compilation failure

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9628:


 Summary: Java 9: ML module compilation failure
 Key: IGNITE-9628
 URL: https://issues.apache.org/jira/browse/IGNITE-9628
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.6
Reporter: Peter Ivanov
 Fix For: 2.7


{code}
[17:56:31]  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project ignite-ml: Compilation failure: Compilation failure: 
[17:56:31]  [ERROR] 
/data/teamcity/work/9198da4c51c3e112/modules/ml/src/main/java/org/apache/ignite/ml/tree/randomforest/data/impurity/MSEHistogram.java:[28,28]
 package sun.reflect.generics.reflectiveObjects is not visible
[17:56:31]  [ERROR]   (package sun.reflect.generics.reflectiveObjects is 
declared in module java.base, which does not export it to the unnamed module)
[17:56:31]  [ERROR] 
/data/teamcity/work/9198da4c51c3e112/modules/ml/src/main/java/org/apache/ignite/ml/tree/randomforest/data/impurity/GiniHistogram.java:[34,28]
 package sun.reflect.generics.reflectiveObjects is not visible
[17:56:31]  [ERROR]   (package sun.reflect.generics.reflectiveObjects is 
declared in module java.base, which does not export it to the unnamed module)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9614) Java 9: Hadoop compilation error

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9614:


 Summary: Java 9: Hadoop compilation error
 Key: IGNITE-9614
 URL: https://issues.apache.org/jira/browse/IGNITE-9614
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.6
Reporter: Peter Ivanov
 Fix For: 2.7


When building Apache Ignite on TeamCity, the following error occurs
{code}
Could not resolve dependencies for project 
org.apache.ignite:ignite-hadoop:jar:2.7.0-SNAPSHOT: Could not find artifact 
jdk.tools:jdk.tools:jar:1.6 at specified path 
/usr/lib/jvm/java-9-oracle/../lib/tools.jar
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Removing "fabric" from Ignite binary package name

[Peter Ivanov]

The task was ready long ago, but community failed to review and merge it
¯\_(ツ)_/¯
Not being a committer, my capabilities of introducing such changes are
limited.

I will update code during this week and will pass for review once again.


On Wed, 1 Aug 2018 at 00:24, Dmitriy Setrakyan 
wrote:

> Yes, agree, fabric has to be removed. If it is done in 2.7, would be great!
>
> On Tue, Jul 31, 2018 at 2:18 PM, Denis Magda  wrote:
>
> > Peter, folks,
> >
> > It's weird, but we have been failing to introduce this minor change since
> > December. Can we get it done for 2.7 that is being discussed at the
> moment?
> > Are there any technical issues that block you from merging the changes?
> >
> > --
> > Denis
> >
> > On Thu, Jun 7, 2018 at 10:03 PM Peter Ivanov 
> wrote:
> >
> > > Ok, then I will update issue code and start preparation for build
> > > configuration changes.
> > >
> > >
> > > On Thu, 7 Jun 2018 at 23:41, Denis Magda  wrote:
> > >
> > > > >
> > > > > With which one — current implementation in issue?
> > > >
> > > >
> > > > That's the answer to your question:
> > > >
> > > > 1. quickly fix all of them (can be solved by preliminary
> preparations —
> > > > searching for -fabric- usages in build configuration);
> > > > 2. update all branches to master because otherwise old branch
> will
> > > stop
> > > > building.
> > > >
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Thu, Jun 7, 2018 at 1:12 PM, Petr Ivanov 
> > wrote:
> > > >
> > > > >
> > > > > > On 7 Jun 2018, at 23:04, Denis Magda  wrote:
> > > > > >
> > > > > > I'm fine with the suggested approach.
> > > > >
> > > > > With which one — current implementation in issue?
> > > > >
> > > > >
> > > > > > However, not sure we need to update
> > > > > > all the branches. Can't branch owners just pull the changes back
> > from
> > > > > > master if the plan to merge back later?
> > > > >
> > > > > Of course, we as an initiative group of this issue should do
> nothing,
> > > it
> > > > > will lie on shoulders of developers.
> > > > >
> > > > >
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > > On Thu, Jun 7, 2018 at 12:57 PM, Petr Ivanov <
> mr.wei...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > >> Denis,
> > > > > >>
> > > > > >>
> > > > > >> The most simple approach — repack and rearchive binary archive
> > after
> > > > > >> release build, however that would not resolve the problem
> globally
> > > > (and
> > > > > >> will require fixing every build configuration we have on
> > TeamCity).
> > > > > >> Current approach implemented in task — creates already correct
> > > folder
> > > > > and
> > > > > >> binary archive name, but old name (with -fabric-) is used in
> > almost
> > > > > every
> > > > > >> build configuration too and merge code to master will require
> to:
> > > > > >>1. quickly fix all of them (can be solved by preliminary
> > > > preparations
> > > > > >> — searching for -fabric- usages in build configuration);
> > > > > >>2. update all branches to master because otherwise old branch
> > > will
> > > > > >> stop building.
> > > > > >>
> > > > > >> WDYT?
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>> On 7 Jun 2018, at 22:42, Denis Magda 
> wrote:
> > > > > >>>
> > > > > >>> Petr,
> > > > > >>>
> > > > > >>> Thanks for pulling up the conversation.
> > > > > >>>
> > > > > >>> I still prefer us not to complicate the things and just remove
> > > > "fabric"
> > > > > >>> from the *package name*. Use the easiest way possible.
> > &

[jira] [Created] (IGNITE-9030) Apache Ignite 2.7 Linux packages version update

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9030:


 Summary: Apache Ignite 2.7 Linux packages version update
 Key: IGNITE-9030
 URL: https://issues.apache.org/jira/browse/IGNITE-9030
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Update DEB and RPM packages' versions in Apache Ignite for the next version 
(2.7)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Peter Ivanov]

Pavel,


Can you give a cue where can be uploaded Nuget packages found?

On Mon, 16 Jul 2018 at 23:37, Pavel Tupitsyn  wrote:

> Petr,
>
> This is the same build that I have linked. Is there anything I should pay
> attention to?
>
> On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov  wrote:
>
> > Pavel,
> >
> >
> > Before uploading, please check this [1] build.
> >
> >
> > [1]
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > <
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > >
> >
> >
> >
> >
> > > On 16 Jul 2018, at 22:56, Pavel Tupitsyn  wrote:
> > >
> > > I will upload NuGet packages. Is this the right TC build?
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
> > >
> > > On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:
> > >
> > >> Ignite site is updated. Most artifacts are published.
> > >>
> > >> Waiting for publishing of Docker images and 2.6 related docs. Also it
> > >> would be great to check NuGet packages.
> > >> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda 
> wrote:
> > >>>
> > >>> Andrey,
> > >>>
> > >>> I'll publish the docs later today.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura 
> wrote:
> > >>>
> >  Dmitry,
> > 
> >  I'm updating the site at this moment. Could somebody publish 2.6
> >  documentation on readme.io site?
> >  On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>
> >  wrote:
> > >
> > > Is there a reason why 2.6 has not been uploaded to the website yet?
> > >
> > > D.
> > >
> > > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
> > >> wrote:
> > >
> > >> Igniters,
> > >>
> > >> Apache Ignite 2.6.0 release (RC1) has been accepted.
> > >>
> > >> 5 "+1" binding votes received:
> > >>
> > >> - Alexey Goncharuk
> > >> - Alexey Kuznetsov
> > >> - Andrey Gura
> > >> - Anton Vinogradov
> > >> - Denis Magda
> > >>
> > >> Vote thread:
> > >>
> > >> *http://apache-ignite-developers.2346864.n4.nabble.
> > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > >>  > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > >>
> > >> Ignite 2.6.0 will be released soon.
> > >>
> > 
> > >>
> >
> >
>

[jira] [Created] (IGNITE-9010) Move web-console build to dedicated root directory

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9010:


 Summary: Move web-console build to dedicated root directory
 Key: IGNITE-9010
 URL: https://issues.apache.org/jira/browse/IGNITE-9010
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Ilya Murchenko


# Move web-console docker image build (web-console, frontend and backend) to 
{{/docker}} directory.
# Prepare README.md file in root of {{/docker}} directory with instructions on 
how to build corresponding image. Remove obsolete per-image README's from 
Dockerfile directories.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8807) Apache Ignite Linux packages 2.6 update

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8807:


 Summary: Apache Ignite Linux packages 2.6 update
 Key: IGNITE-8807
 URL: https://issues.apache.org/jira/browse/IGNITE-8807
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.6


Update RPM and DEB packages' specifications for 2.6 release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Removing "fabric" from Ignite binary package name

[Peter Ivanov]

Ok, then I will update issue code and start preparation for build
configuration changes.


On Thu, 7 Jun 2018 at 23:41, Denis Magda  wrote:

> >
> > With which one — current implementation in issue?
>
>
> That's the answer to your question:
>
> 1. quickly fix all of them (can be solved by preliminary preparations —
> searching for -fabric- usages in build configuration);
> 2. update all branches to master because otherwise old branch will stop
> building.
>
>
> --
> Denis
>
> On Thu, Jun 7, 2018 at 1:12 PM, Petr Ivanov  wrote:
>
> >
> > > On 7 Jun 2018, at 23:04, Denis Magda  wrote:
> > >
> > > I'm fine with the suggested approach.
> >
> > With which one — current implementation in issue?
> >
> >
> > > However, not sure we need to update
> > > all the branches. Can't branch owners just pull the changes back from
> > > master if the plan to merge back later?
> >
> > Of course, we as an initiative group of this issue should do nothing, it
> > will lie on shoulders of developers.
> >
> >
> > >
> > > --
> > > Denis
> > >
> > > On Thu, Jun 7, 2018 at 12:57 PM, Petr Ivanov 
> > wrote:
> > >
> > >> Denis,
> > >>
> > >>
> > >> The most simple approach — repack and rearchive binary archive after
> > >> release build, however that would not resolve the problem globally
> (and
> > >> will require fixing every build configuration we have on TeamCity).
> > >> Current approach implemented in task — creates already correct folder
> > and
> > >> binary archive name, but old name (with -fabric-) is used in almost
> > every
> > >> build configuration too and merge code to master will require to:
> > >>1. quickly fix all of them (can be solved by preliminary
> preparations
> > >> — searching for -fabric- usages in build configuration);
> > >>2. update all branches to master because otherwise old branch will
> > >> stop building.
> > >>
> > >> WDYT?
> > >>
> > >>
> > >>
> > >>> On 7 Jun 2018, at 22:42, Denis Magda  wrote:
> > >>>
> > >>> Petr,
> > >>>
> > >>> Thanks for pulling up the conversation.
> > >>>
> > >>> I still prefer us not to complicate the things and just remove
> "fabric"
> > >>> from the *package name*. Use the easiest way possible.
> > >>>
> > >>> Personally, I don't care about Hadoop and would not suggest the
> > community
> > >>> wasting its time on it. So, just rename the suffixes/prefixes of the
> > >> build
> > >>> files the way you like to address Anton's concerns.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>>
> > >>> On Thu, Jun 7, 2018 at 1:49 AM, Petr Ivanov 
> > wrote:
> > >>>
> >  Igniters,
> > 
> > 
> >  Lets define once again what should be done in this [1] task?
> >  If current implementation is good, than I’ll update it to master and
> > >> pass
> >  for review.
> > 
> >  Yet, there is other part of the task which concerns our build server
> > — I
> >  assume that almost all our build configurations will fail due to
> name
> >  change and there is no simple way of updating configurations other
> > then
> >  merge task to master and start fixing failing builds.
> > 
> > 
> >  [1] https://issues.apache.org/jira/browse/IGNITE-7251
> > 
> > 
> > 
> > > On 10 Feb 2018, at 01:56, Denis Magda  wrote:
> > >
> > >> I don't think we necessarily need to remove 'fabric' word from
> every
> >  file
> > >> in the project, we just need to rename the name of downloadable
> > >> package.
> > >
> > > Couldn’t say it better than you, Val. Thanks for pitching in :)
> This
> > is
> >  exactly what the ticket is about.
> > >
> > > —
> > > Denis
> > >
> > >> On Feb 9, 2018, at 11:53 AM, Valentin Kulichenko <
> >  valentin.kuliche...@gmail.com> wrote:
> > >>
> > >> Anton,
> > >>
> > >> I don't think we necessarily need to remove 'fabric' word from
> every
> >  file
> > >> in the project, we just need to rename the name of downloadable
> >  package. Is
> > >> there any other place where 'fabric' is exposed to the user?
> > >>
> > >> If that's the case, it should not be a big change, no?
> > >>
> > >> -Val
> > >>
> > >> On Fri, Feb 9, 2018 at 3:49 AM, Anton Vinogradov <
> >  avinogra...@gridgain.com>
> > >> wrote:
> > >>
> > >>> Denis,
> > >>>
> > >>> You're proposing changes without viewing a code :)
> > >>>
> > >>>
> > >>> On Thu, Feb 8, 2018 at 10:07 PM, Denis Magda 
> >  wrote:
> > >>>
> >  Anton,
> > 
> >  What’s wrong if we just go ahead and:
> >  - replace “fabric” with “ignite”
> >  - replace “hadoop” with “ignite-hadoop"
> > 
> >  —
> >  Denis
> > 
> > > On Feb 8, 2018, at 1:51 AM, Anton Vinogradov <
> >  avinogra...@gridgain.com
> > 
> >  wrote:
> > >
> > > Denis,
> > >
> > > "hadoop" and "fabric" words work on same engine.
> > >
> > 

Re: Apache Ignite 2.6 - Packages roadmap

[Peter Ivanov]

On Fri, 8 Jun 2018 at 00:37, Denis Magda  wrote:

> Petr,
>
> Am I correct that all 3 points were tested for VirtualBox?


No, it was tested for Windows 10 WSL.


I would
> introduce a documentation sub-section for VirtualBox then.


As I said previously — under “honest” virtual environments (i. e.
VirtualBox, VMWare, Hyper-V, etc.) everything will work just as on the bare
metal. And no special section is required, otherwise you will end up
describing support of every virtualization technology in the world. I would
suggest we wait for some user and dev experience about using packages in
virtual and containerized environments to better understand what should be
mentioned in documentation and what should not.



>
> As for the Windows WSL, did you have a change to look into it?
>
> --
> Denis
>
> On Thu, Jun 7, 2018 at 2:42 AM, Petr Ivanov  wrote:
>
> > Here are the results of checks:
> >
> >
> > 1. Ubuntu. Running Apache Ignite as a stand-alone application works fine,
> > I have successful connections to another Apache Ignite node running under
> > VirtualBox CentOS.
> > NOTE: connectivity started working only after creation of “allow all
> > incoming connections” rule in Windows Defender Firewall.
> >
> > 2. Debian. Running Apache Ignite as a stand-alone application works fine,
> > I have successful connections to another Apache Ignite node running under
> > VirtualBox CentOS.
> > NOTE: in addition to Ubuntu’s NOTE, it is required to install dirmngr
> > program for apt-key be able to download gpg keys over network (this NOTE
> > can be added to documentation + I can add dependency to DEB package in
> next
> > release).
> >
> > 3. SUSE. Has neither APT no YUM commands. RPM package can be installed
> via
> > rpm -i command, but I think that this case is out of Apache Ignite 2.5
> > scope and the question of “officially supported Linux distributions”
> should
> > be discussed separately.
> >
> >
> >
> >
> > > On 7 Jun 2018, at 08:43, Peter Ivanov  wrote:
> > >
> > > Understood. Will do today.
> > >
> > >
> > > On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan  > <mailto:dsetrak...@apache.org>> wrote:
> > > On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov  > <mailto:mr.wei...@gmail.com>> wrote:
> > >
> > > > Dmitriy,
> > > >
> > > >
> > > > What kind of instructions? Systemd or stand-alone?
> > > > I thought we have already agreed that systemd services are not
> > eligible for
> > > > Windows 10 WSL.
> > > >
> > > > So have I to check that Debian, Ubuntu and SUSE environments for
> > Windows 10
> > > > WSL supports running Apache Ignite installed from packages as a
> > stand-alone
> > > > application?
> > > >
> > >
> > > Yes.
> >
> >
>

Re: Apache Ignite 2.6 - Packages roadmap

[Peter Ivanov]

Understood. Will do today.


On Thu, 7 Jun 2018 at 08:43, Dmitriy Setrakyan 
wrote:

> On Wed, Jun 6, 2018 at 10:40 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> >
> > What kind of instructions? Systemd or stand-alone?
> > I thought we have already agreed that systemd services are not eligible
> for
> > Windows 10 WSL.
> >
> > So have I to check that Debian, Ubuntu and SUSE environments for Windows
> 10
> > WSL supports running Apache Ignite installed from packages as a
> stand-alone
> > application?
> >
>
> Yes.
>

Re: Apache Ignite 2.6 - Packages roadmap

[Peter Ivanov]

Dmitriy,


What kind of instructions? Systemd or stand-alone?
I thought we have already agreed that systemd services are not eligible for
Windows 10 WSL.

So have I to check that Debian, Ubuntu and SUSE environments for Windows 10
WSL supports running Apache Ignite installed from packages as a stand-alone
application?



On Thu, 7 Jun 2018 at 08:01, Dmitriy Setrakyan 
wrote:

> Petr,
>
> I confirm that Ignite starts for me from a downloadable archive on Ubuntu
> under Windows 10.
>
> I would actually recommend that instead of discussing here how running
> Linux in Windows 10 is not a valid use case, we should probably just test
> it and fix it. Can you please try running your instructions in Ubuntu,
> Debian, and Suse on Windows 10 and confirm that they work for you?
>
> None of them have worked for me so far. I consider this to be a critical
> issue.
>
> D.
>
> On Wed, Jun 6, 2018 at 9:44 PM, Peter Ivanov  wrote:
>
> > Denis,
> >
> >
> > The question “will Apache Ignite start under Windows 10 WSL Ubuntu from
> > packages?” is the same as “will Apache Ignite start under Windows 10 WSL
> > Ubuntu from binary archive?” concerning running Apache Ignite as
> standalone
> > service (from ignite.sh). Did anyone from community tried running Apache
> > Ignite from the binary archive under Windows 10 WSL Ubuntu?
> >
> > So the problem is not the package itself, but environment. When I was
> > preparing packages - there was no mention about complex experimental
> > environments which should be supported, so I do not understand
> > this aggresive criticism concerning revealed problem.
> >
> > Of course, I will check running Apache Ignite from packages under Windows
> > 10 WSL Ubuntu as a stand-alone application, but, IMO, that had to be done
> > as soon as Windows 10 WSL Ubuntu environment was introduced in the first
> > place, yet, I do not see such thread among dev-list discussions.
> >
> >
> >
> > On Thu, 7 Jun 2018 at 03:02, Denis Magda  wrote:
> >
> > > Stop. I've finally figured out what kind of environment Dmitriy is
> > talking
> > > about.
> > >
> > > Imagine a Windows developer who needs to run something under Linux on
> his
> > > machine. He/she would go for VirtualBox and Parallels Desktop. Hope, we
> > > don't have any doubts that it needs to be possible to install Ignite
> via
> > > DEB|RPM in those virtual environments.
> > >
> > > Dmitriy, is talking about an alternate solution for VirtualBox and
> > > Parallels that became default since Windows 10.
> > >
> > > Considering this we must ensure Ignite RPM|DEB works there. Backing up
> > > Dmitriy.
> > >
> > > Petr, do you have access to a Windows 10 machine?
> > >
> > > --
> > > Denis
> > >
> > >
> > > On Wed, Jun 6, 2018 at 9:56 AM, Peter Ivanov 
> > wrote:
> > >
> > > > Denis,
> > > >
> > > >
> > > > I’ll look into it
> > > >
> > > >
> > > > On Wed, 6 Jun 2018 at 19:17, Denis Magda  wrote:
> > > >
> > > > > I suggest us trying to move the conversation in this direction.
> > > > >
> > > > > Is it possible to install and run Cassandra using DEB from that
> > > emulation
> > > > > environment on Windows? If yes, then we should spend our efforts
> > > adopting
> > > > > Ignite for the environment. Otherwise, we should skip it for now.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > > On Tue, Jun 5, 2018 at 5:57 PM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > > > On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov <
> mr.wei...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Dmitriy,
> > > > > > >
> > > > > > >
> > > > > > > I will check soon and see what can be done to overcome this.
> > > > > > >
> > > > > >
> > > > > > Thanks! Looking forward to your feedback.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Yet, I still doubt that running Apache Ignite packed in DEB
> under
> > > > > Windows
> > > > > > > 10 WSL Ubuntu is a plausible user case.
> > > > > > >
> > > > > >
> > > > > > Disagree, it will be used during development, not production.
> > Windows
> > > > 10
> > > > > > supports a clean way of running Linux - you simply just download
> > and
> > > > > > install it from the Windows app store. Many developers who use
> > > Windows
> > > > > will
> > > > > > try it.
> > > > > >
> > > > > >
> > > > > > > To be honest, I doubt that our packages are being downloaded
> and
> > > > > > installed
> > > > > > > at all...
> > > > > > >
> > > > > >
> > > > > > Well, if we keep the packages unusable, then no one will ever use
> > > them.
> > > > > > Many people likely tried and gave up. Let's make sure that after
> > you
> > > > > > address all the issues, the experience with packages will be
> > smooth.
> > > > > >
> > > > > > D.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Apache Ignite 2.6 - Packages roadmap

[Peter Ivanov]

Denis,


The question “will Apache Ignite start under Windows 10 WSL Ubuntu from
packages?” is the same as “will Apache Ignite start under Windows 10 WSL
Ubuntu from binary archive?” concerning running Apache Ignite as standalone
service (from ignite.sh). Did anyone from community tried running Apache
Ignite from the binary archive under Windows 10 WSL Ubuntu?

So the problem is not the package itself, but environment. When I was
preparing packages - there was no mention about complex experimental
environments which should be supported, so I do not understand
this aggresive criticism concerning revealed problem.

Of course, I will check running Apache Ignite from packages under Windows
10 WSL Ubuntu as a stand-alone application, but, IMO, that had to be done
as soon as Windows 10 WSL Ubuntu environment was introduced in the first
place, yet, I do not see such thread among dev-list discussions.



On Thu, 7 Jun 2018 at 03:02, Denis Magda  wrote:

> Stop. I've finally figured out what kind of environment Dmitriy is talking
> about.
>
> Imagine a Windows developer who needs to run something under Linux on his
> machine. He/she would go for VirtualBox and Parallels Desktop. Hope, we
> don't have any doubts that it needs to be possible to install Ignite via
> DEB|RPM in those virtual environments.
>
> Dmitriy, is talking about an alternate solution for VirtualBox and
> Parallels that became default since Windows 10.
>
> Considering this we must ensure Ignite RPM|DEB works there. Backing up
> Dmitriy.
>
> Petr, do you have access to a Windows 10 machine?
>
> --
> Denis
>
>
> On Wed, Jun 6, 2018 at 9:56 AM, Peter Ivanov  wrote:
>
> > Denis,
> >
> >
> > I’ll look into it
> >
> >
> > On Wed, 6 Jun 2018 at 19:17, Denis Magda  wrote:
> >
> > > I suggest us trying to move the conversation in this direction.
> > >
> > > Is it possible to install and run Cassandra using DEB from that
> emulation
> > > environment on Windows? If yes, then we should spend our efforts
> adopting
> > > Ignite for the environment. Otherwise, we should skip it for now.
> > >
> > > --
> > > Denis
> > >
> > > On Tue, Jun 5, 2018 at 5:57 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > > wrote:
> > >
> > > > On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov 
> > > wrote:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > >
> > > > > I will check soon and see what can be done to overcome this.
> > > > >
> > > >
> > > > Thanks! Looking forward to your feedback.
> > > >
> > > >
> > > > >
> > > > > Yet, I still doubt that running Apache Ignite packed in DEB under
> > > Windows
> > > > > 10 WSL Ubuntu is a plausible user case.
> > > > >
> > > >
> > > > Disagree, it will be used during development, not production. Windows
> > 10
> > > > supports a clean way of running Linux - you simply just download and
> > > > install it from the Windows app store. Many developers who use
> Windows
> > > will
> > > > try it.
> > > >
> > > >
> > > > > To be honest, I doubt that our packages are being downloaded and
> > > > installed
> > > > > at all...
> > > > >
> > > >
> > > > Well, if we keep the packages unusable, then no one will ever use
> them.
> > > > Many people likely tried and gave up. Let's make sure that after you
> > > > address all the issues, the experience with packages will be smooth.
> > > >
> > > > D.
> > > >
> > >
> >
>

Re: Ignite mvn compilation with skiptest

[Peter Ivanov]

Hi!


Can you just not specify -DskipTests as it is default to false?
Also, be warned that with all that enabled profiles you’re going to have
about 50 hours of tests (~47000 units) during build, some of which require
specific JVM options and OS tuning (like PDS or AOP, for example).


On Wed, 6 Jun 2018 at 19:55, vbm  wrote:

> Ignite mvn compilation with skiptest as false is throwing class not found
> errors:
>
> [ERROR] warning(junit.framework.TestSuite$1)  Time elapsed: 0 s  <<<
> FAILURE!
> junit.framework.AssertionFailedError:
> Exception in constructor: testCreateDropCache
> (java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.testframework.config.GridTestProperties
>
> Command used:
> mvn clean install -Pall-java,all-scala,licenses -DskipTests=false
>
> How to compile with skiptest as false ?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Apache Ignite 2.6 - Packages roadmap

[Peter Ivanov]

Denis,


I’ll look into it


On Wed, 6 Jun 2018 at 19:17, Denis Magda  wrote:

> I suggest us trying to move the conversation in this direction.
>
> Is it possible to install and run Cassandra using DEB from that emulation
> environment on Windows? If yes, then we should spend our efforts adopting
> Ignite for the environment. Otherwise, we should skip it for now.
>
> --
> Denis
>
> On Tue, Jun 5, 2018 at 5:57 PM, Dmitriy Setrakyan 
> wrote:
>
> > On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov 
> wrote:
> >
> > > Dmitriy,
> > >
> > >
> > > I will check soon and see what can be done to overcome this.
> > >
> >
> > Thanks! Looking forward to your feedback.
> >
> >
> > >
> > > Yet, I still doubt that running Apache Ignite packed in DEB under
> Windows
> > > 10 WSL Ubuntu is a plausible user case.
> > >
> >
> > Disagree, it will be used during development, not production. Windows 10
> > supports a clean way of running Linux - you simply just download and
> > install it from the Windows app store. Many developers who use Windows
> will
> > try it.
> >
> >
> > > To be honest, I doubt that our packages are being downloaded and
> > installed
> > > at all...
> > >
> >
> > Well, if we keep the packages unusable, then no one will ever use them.
> > Many people likely tried and gave up. Let's make sure that after you
> > address all the issues, the experience with packages will be smooth.
> >
> > D.
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


You suggest removing fully working under corresponding Linux distributive
RPM and DEB packages entirely from apache.org/dist/ignite only because they
do not work in highly unlikely scenario (Windows 10 WSL) as service?

I will certainly add reference about running Apache Ignite from the
packages as standalone Java application (with corresponding permissions
note) but I’d like to hear community opinion on the whole matter -
everything that was done, was done with review and approve from lots of
Apache Ignite commiters and PMCs, including PMC chair.


On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
wrote:

> Peter,
>
> I have reopened this ticket:
> https://issues.apache.org/jira/browse/IGNITE-8671
>
> I changed the priority to blocker. At this point I suggest the following:
> - we either remove the DEB and RPM packages from the website and readme
> - or we fix this issue ASAP as stated in the ticket.
>
> I will leave it up to you to decide.
>
> D.
>
> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> wrote:
>
>> Dmitriy,
>>
>>
>> SystemD supports running multiple instances of one service – this is done
>> through @-like syntax: 'sudo systemctl start apache-ignite@> file name>', so that with every unique command string there will be
>> started
>> / stopped unique instance of Apache Ignite. And all instances can be
>> restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
>> systemctl  apache-ignite@*'.
>>
>> Still, I can add a note about possibility of starting Apache Ignite
>> manually through ignite.sh with a reference to corresponding documentation
>> section, information where to look for the root of Apache Ignite
>> installation and how to correctly start Apache Ignite in terms of
>> permissions.
>>
>> File the documentation updates ticket?
>>
>>
>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
>> wrote:
>>
>> > Petr,
>> >
>> > Most of the users will download and install Ignite so they can develop
>> with
>> > it. This means that they will be starting more than one node, which is
>> > impossible if Ignite is a service. We should provide instructions to do
>> > both.
>> >
>> > D.
>> >
>> > On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
>> wrote:
>> >
>> > > Dmitriy,
>> > >
>> > >
>> > > Current packages design (both RPM and DEB) was reviewed and approved
>> by
>> > > community. I do not quite remember why service-based startup was
>> chosen
>> > but
>> > > it seems rather logical and Unix-compliant – under Linux almost every
>> > > service software is packed this way, which gives some benefits like
>> > service
>> > > autostart on reboot, centralized running nodes management (through
>> > > systemctl), etc. There is no point in packing binary into Linux
>> packages
>> > if
>> > > it then will be used as standalone executable.
>> > > Yet, current design does not limit advanced user from running Apache
>> > Ignite
>> > > as standalone process – executing
>> /usr/share/apache-ignite/bin/ignite.sh
>> > > with parameters will start Apache Ignite node as if it was delivered
>> by
>> > > binary archive.
>> > >
>> > >
>> > >
>> > > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > > wrote:
>> > >
>> > > > Petr,
>> > > >
>> > > > Why do we even suggest starting Ignite as a service? Why not just
>> start
>> > > > Ignite instance as a stand-alone process? This should work, no?
>> > > >
>> > > > D.
>> > > >
>> > > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
>> > > wrote:
>> > > >
>> > > > > Unfortunately, it seems to be impossible (at least for now) — [1].
>> > > > > So we can say that current package design is for native Linux
>> > > > installation
>> > > > > only.
>> > > > >
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671?
>> > > > > focusedCommentId=16496813&page=com.atlassian.jira.
>> > > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
>> > > > >
>> > > > >
>> > > > > > On 31 May 2018, at 18:22, Petr Ivanov 
>> wrote:
>> > > > > >
>> > > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
>> > > > > https://issues.apache.org/jira/browse/IGNITE-8671>
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
>> > dsetrak...@apache.org
>> > > > > <mailto:dsetrak...@apache.org>> wrote:
>> > > > > >>
>> > > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov <
>> mr.wei...@gmail.com
>> > > > > <mailto:mr.wei...@gmail.com>> wrote:
>> > > > > >>
>> > > > > >>> I’ll start the investigation.
>> > > > > >>>
>> > > > > >>
>> > > > > >> Can you please file a ticket so we can track it?
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


SystemD supports running multiple instances of one service – this is done
through @-like syntax: 'sudo systemctl start apache-ignite@', so that with every unique command string there will be started
/ stopped unique instance of Apache Ignite. And all instances can be
restarted / stopped / enabled on boot / etc. simultaneously through 'sudo
systemctl  apache-ignite@*'.

Still, I can add a note about possibility of starting Apache Ignite
manually through ignite.sh with a reference to corresponding documentation
section, information where to look for the root of Apache Ignite
installation and how to correctly start Apache Ignite in terms of
permissions.

File the documentation updates ticket?


On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
wrote:

> Petr,
>
> Most of the users will download and install Ignite so they can develop with
> it. This means that they will be starting more than one node, which is
> impossible if Ignite is a service. We should provide instructions to do
> both.
>
> D.
>
> On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> >
> > Current packages design (both RPM and DEB) was reviewed and approved by
> > community. I do not quite remember why service-based startup was chosen
> but
> > it seems rather logical and Unix-compliant – under Linux almost every
> > service software is packed this way, which gives some benefits like
> service
> > autostart on reboot, centralized running nodes management (through
> > systemctl), etc. There is no point in packing binary into Linux packages
> if
> > it then will be used as standalone executable.
> > Yet, current design does not limit advanced user from running Apache
> Ignite
> > as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
> > with parameters will start Apache Ignite node as if it was delivered by
> > binary archive.
> >
> >
> >
> > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan 
> > wrote:
> >
> > > Petr,
> > >
> > > Why do we even suggest starting Ignite as a service? Why not just start
> > > Ignite instance as a stand-alone process? This should work, no?
> > >
> > > D.
> > >
> > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> > wrote:
> > >
> > > > Unfortunately, it seems to be impossible (at least for now) — [1].
> > > > So we can say that current package design is for native Linux
> > > installation
> > > > only.
> > > >
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-8671?
> > > > focusedCommentId=16496813&page=com.atlassian.jira.
> > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> > > >
> > > >
> > > > > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> > > > >
> > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > > > https://issues.apache.org/jira/browse/IGNITE-8671>
> > > > >
> > > > >
> > > > >
> > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > > > <mailto:dsetrak...@apache.org>> wrote:
> > > > >>
> > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > > > <mailto:mr.wei...@gmail.com>> wrote:
> > > > >>
> > > > >>> I’ll start the investigation.
> > > > >>>
> > > > >>
> > > > >> Can you please file a ticket so we can track it?
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,


Current packages design (both RPM and DEB) was reviewed and approved by
community. I do not quite remember why service-based startup was chosen but
it seems rather logical and Unix-compliant – under Linux almost every
service software is packed this way, which gives some benefits like service
autostart on reboot, centralized running nodes management (through
systemctl), etc. There is no point in packing binary into Linux packages if
it then will be used as standalone executable.
Yet, current design does not limit advanced user from running Apache Ignite
as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh
with parameters will start Apache Ignite node as if it was delivered by
binary archive.



On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan 
wrote:

> Petr,
>
> Why do we even suggest starting Ignite as a service? Why not just start
> Ignite instance as a stand-alone process? This should work, no?
>
> D.
>
> On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov  wrote:
>
> > Unfortunately, it seems to be impossible (at least for now) — [1].
> > So we can say that current package design is for native Linux
> installation
> > only.
> >
> >
> > https://issues.apache.org/jira/browse/IGNITE-8671?
> > focusedCommentId=16496813&page=com.atlassian.jira.
> > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813
> >
> >
> > > On 31 May 2018, at 18:22, Petr Ivanov  wrote:
> > >
> > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 <
> > https://issues.apache.org/jira/browse/IGNITE-8671>
> > >
> > >
> > >
> > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan  > > wrote:
> > >>
> > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov  > > wrote:
> > >>
> > >>> I’ll start the investigation.
> > >>>
> > >>
> > >> Can you please file a ticket so we can track it?
> > >
> >
> >
>

[jira] [Created] (IGNITE-8671) Provide instructions on running Apache Ignite as systemd service on Windows 10 WSL Ubuntu

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8671:


 Summary: Provide instructions on running Apache Ignite as systemd 
service on Windows 10 WSL Ubuntu
 Key: IGNITE-8671
 URL: https://issues.apache.org/jira/browse/IGNITE-8671
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Prepare instructions (and possibly update official documentation) on running 
Apache Ignite as systemd service on Windows 10 WSL Ubuntu using official DEB 
package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,

Can you try starting dbus manually? sudo service dbus start

If it still does not work, I will have to held an investigation on running
systemd services on Windows 10 WSL


On Thu, 31 May 2018 at 00:31, Dmitriy Setrakyan 
wrote:

> On Wed, May 30, 2018 at 2:09 PM, Peter Ivanov  wrote:
>
> > Dmitriy,
> >
> > What kind of Ubuntu installation do you have (and what version)?
> > Is it WSL under Windows 10 or containerized (docker)?
> >
> >
> Windows Ubuntu App -
> https://docs.microsoft.com/en-us/windows/wsl/install-win10
>
> D.
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Peter Ivanov]

Dmitriy,

What kind of Ubuntu installation do you have (and what version)?
Is it WSL under Windows 10 or containerized (docker)?


On Wed, 30 May 2018 at 19:52, Dmitriy Setrakyan 
wrote:

> Petr,
>
> I have finally was able to install Ignite Debian package. But then I got
> stuck at the very next instruction:
>
>
> > *d@DmitriyPC:~$ sudo systemctl start
> > apache-ignite@default-config.xmlFailed to connect to bus: No such file
> or
> > directory*
>
>
> D.
>
> On Wed, May 30, 2018 at 7:40 AM, Petr Ivanov  wrote:
>
> > Sometimes Ubuntu with requested and dependency packages recommends
> > additional packages (which is controlled by corresponding directive in
> > package).
> > This option --no-install-recommends makes sure that these packages will
> be
> > skipped and overall installation will be more compact and precise.
> >
> > There is no such option for YUM (as far as I am aware of).
> >
> >
> >
> > > On 30 May 2018, at 17:16, Dmitriy Setrakyan 
> > wrote:
> > >
> > > Petr,
> > >
> > > Can you tell me what this flag does: "--no-install-recommends"?
> > >
> > > I am seeing that it is set for Debian, but not for RPM.
> > >
> > > D.
> > >
> > > On Wed, May 30, 2018 at 7:07 AM, Petr Ivanov 
> > wrote:
> > >
> > >> Of course: https://apacheignite.readme.io/docs/getting-started#
> > >> alternative-installation-options  > >> io/docs/getting-started#alternative-installation-options>
> > >> Snippet "DEB repository setup"
> > >>
> > >>
> > >>
> > >>
> > >>> On 30 May 2018, at 16:59, Dmitriy Setrakyan 
> > >> wrote:
> > >>>
> > >>> Petr, can you provide a link to the Debian snippet on readme.io? I
> > >> cannot
> > >>> find it.
> > >>>
> > >>> On Wed, May 30, 2018 at 6:16 AM, Petr Ivanov 
> > >> wrote:
> > >>>
> >  Docker images for Apache Ignite [1] and Web Console [2] 2.5.0 are
> > >> uploaded.
> > 
> > 
> >  [1] https://hub.docker.com/r/apacheignite/ignite/tags
> >  [2] https://hub.docker.com/r/apacheignite/web-console-
> > standalone/tags/
> > 
> > 
> > 
> > > On 30 May 2018, at 06:55, Petr Ivanov  wrote:
> > >
> > > Instructions for RPM Package Installation (snippet with repository
> >  configuration) at ignite.apache.org  are
> >  obsolete and should be replaced by apacheignite.readme.io <
> >  http://apacheignite.readme.io/> snippet.
> > >
> > >
> > >
> > >> On 30 May 2018, at 02:57, Prachi Garg   >  pg...@gridgain.com>> wrote:
> > >>
> > >> Peter,
> > >>
> > >> I updated the RPM and DEB description on the downloads page[1]
> >  (following the instructions on the documentation [2]). Please check
> > that
> >  the repositories and installation instructions are up-to-date.
> > >>
> > >> [1] https://ignite.apache.org/download.cgi#rpm-package <
> >  https://ignite.apache.org/download.cgi#rpm-package>
> > >> [2] https://apacheignite.readme.io/docs/getting-started#
> >  section-rpm-deb-packages-installation  >  io/docs/getting-started#section-rpm-deb-packages-installation>
> > >>
> > >> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan <
> >  dsetrak...@apache.org > wrote:
> > >> I just tried the Debian install. This is what I got after
> executing
> >  "sudo
> > >> apt get" command:
> > >>
> > >>
> > >>>
> > >>> *E: The repository 'https://apache.org/dist/ignite/deb <
> >  https://apache.org/dist/ignite/deb>
> > >>>  >  ignite/deb>> apache-ignite Release' does not have a
> > >>> Release file.N: Updating from such a repository can't be done
> >  securely, and
> > >>> is therefore disabled by default.N: See apt-secure(8) manpage for
> > >>> repository creation and user configuration details.*
> > >>
> > >>
> > >> D.
> > >>
> > >> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  >  > wrote:
> > >>
> > >>> Andrey,
> > >>>
> > >>> Please help to generate 2.5 release HTML file and add it to
> Ignite
> >  website
> > >>> SVN. Sergey K and Ilya S. should be able to assist with this.
> > >>>
> > >>> Sergey Chugunov and Ivan R., finalize the docs as soon as you
> can.
> > We
> > >>> can't announce the release and close it without having the docs
> > done.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>>
> > >>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  >  > wrote:
> > >>>
> >  Folks,
> > 
> >  I have released 2.5 documentation on readme.io <
> http://readme.io/
> > >.
> >  Also, the downloads page
> >  on
> >  the website is updated with 2.5 release. Mauricio will work on
> >  updating
> >  the
> >  latest doc reference.
> > 
> > 
> >

[jira] [Created] (IGNITE-8586) Minor fix for Apache Ignite's release procedure

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8586:


 Summary: Minor fix for Apache Ignite's release procedure
 Key: IGNITE-8586
 URL: https://issues.apache.org/jira/browse/IGNITE-8586
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Fix package.sh to not require sudo permissions for packages build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8543) Node.js tests count with debug on/off differs

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8543:


 Summary: Node.js tests count with debug on/off differs
 Key: IGNITE-8543
 URL: https://issues.apache.org/jira/browse/IGNITE-8543
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Running Node,js thin client tests with debug turned on / off results in 
different total test count 
([64|https://ci.ignite.apache.org/viewLog.html?buildId=1316067&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ThinClientNodeJs]
 and 
[99|https://ci.ignite.apache.org/viewLog.html?buildId=1316268&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ThinClientNodeJs]
 respectively. Thats not predicted behaviour and require investigation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8510) RPM package 2.4.0 is incorrectly upgraded by 2.5.0

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8510:


 Summary: RPM package 2.4.0 is incorrectly upgraded by 2.5.0
 Key: IGNITE-8510
 URL: https://issues.apache.org/jira/browse/IGNITE-8510
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Due to incorrect path to {{_sharedstatedir}} variable, RPM package 2.4.0 was 
built with {{/usr/com/apache-ignite}} as main work directory (instead of 
{{/var/lib/apache-ignite}}) and during upgrade procedure, postinstall script of 
2.5.0 does not update permissions for correct directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8496) Check necessity of JDK check in SqlLine script

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8496:


 Summary: Check necessity of JDK check in SqlLine script
 Key: IGNITE-8496
 URL: https://issues.apache.org/jira/browse/IGNITE-8496
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.5
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.6


Investigate the necessity of JDK checks in SqlLine scripts (both sh and cmd).
Currently, it check that Java has version 1.8 or 9. With current Java release 
cycle, regular updating of this check can be excessive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8478) SqlLine run failure on Java 9

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8478:


 Summary: SqlLine run failure on Java 9
 Key: IGNITE-8478
 URL: https://issues.apache.org/jira/browse/IGNITE-8478
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


{code}
*The version of JAVA installed in C:\Program Files\Java\jdk-9.0.1 is
incorrect.*
*Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8.**You
can also download latest JDK at http://java.com/download
<http://java.com/download>.*
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8461:


 Summary: Scala-2.10 modules compilation failure under JDK 9
 Key: IGNITE-8461
 URL: https://issues.apache.org/jira/browse/IGNITE-8461
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.4
Reporter: Peter Ivanov
 Fix For: 2.5


{code}
[ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
[INFO]  at 
scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
[INFO]  at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
[INFO]  at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
[INFO]  at 
scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
[INFO]  at 
scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
[INFO]  at 
scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
[INFO]  at 
scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
[INFO]  at scala.collection.Iterator$class.foreach(Iterator.scala:727)
[INFO]  at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
[INFO]  at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
[INFO]  at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
[INFO]  at 
scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
[INFO]  at scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
[INFO]  at 
scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
[INFO]  at 
scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
[INFO]  at scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
[INFO]  at scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
[INFO]  at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
[INFO]  at scala.tools.nsc.Global.rootMirror(Global.scala:57)
[INFO]  at scala.tools.nsc.Global.rootMirror(Global.scala:37)
[INFO]  at 
scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
[INFO]  at 
scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
[INFO]  at 
scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
[INFO]  at scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
[INFO]  at scala.tools.nsc.Global$Run.(Global.scala:1290)
[INFO]  at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
[INFO]  at scala.tools.nsc.Main$.doCompile(Main.scala:79)
[INFO]  at scala.tools.nsc.Driver.process(Driver.scala:54)
[INFO]  at scala.tools.nsc.Driver.main(Driver.scala:67)
[INFO]  at scala.tools.nsc.Main.main(Main.scala)
[INFO]  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[INFO]  at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]  at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[INFO]  at scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
[INFO]  at 
scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
[INFO]
[INFO] java.lang.reflect.InvocationTargetException
[INFO]  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[INFO]  at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]  at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[INFO]  at scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
[INFO]  at 
scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
[ERROR] Caused by: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
[INFO]  at 
scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
[INFO]  at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
[INFO]  at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
[INFO]  at 
scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
[INFO]  at 
scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
[INFO]  at scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
[INFO]  at

[jira] [Created] (IGNITE-8454) Hadoop module compilation failure under JDK9

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8454:


 Summary: Hadoop module compilation failure under JDK9
 Key: IGNITE-8454
 URL: https://issues.apache.org/jira/browse/IGNITE-8454
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov


Reproduced on Linux (Mac is OK)
{code}
[16:38:27][Step 4/5] [ERROR] Failed to execute goal on project ignite-hadoop: 
Could not resolve dependencies for project 
org.apache.ignite:ignite-hadoop:jar:2.5.0-SNAPSHOT: Could not find artifact 
jdk.tools:jdk.tools:jar:1.6 at specified path 
/usr/lib/jvm/java-9-oracle/../lib/tools.jar
{code}
Possibly relates to Scala 2.10-2.11: 
https://lists.apache.org/thread.html/%3caf9b21681d3ee94aa935901747be4b813a3b4...@shsmsx101.ccr.corp.intel.com%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8452) ML module compilation failure under Java 9

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8452:


 Summary: ML module compilation failure under Java 9
 Key: IGNITE-8452
 URL: https://issues.apache.org/jira/browse/IGNITE-8452
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.4
Reporter: Peter Ivanov
 Fix For: 2.5


Running Apache Ignite build on master branch (commit: ) fails with following 
error:
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile 
(default-testCompile) on project ignite-ml: Compilation failure: Compilation 
failure:
[ERROR] 
/Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[62,45]
 incompatible types: java.lang.Object cannot be converted to java.lang.Integer
[ERROR] 
/Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[74,38]
 incompatible types: java.lang.Object cannot be converted to java.lang.Integer
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8441) Java 9 (Stage II)

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8441:


 Summary: Java 9 (Stage II)
 Key: IGNITE-8441
 URL: https://issues.apache.org/jira/browse/IGNITE-8441
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Enhance [Ignite Tests 2.4+ (Java 
8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview]
 project with ability to run build and tests under JDK9. Fix all incoming 
problems so that full Run All test runs on same branches provide similar 
results (excluding flaky tests).

Some known problems:
* some current versions of used maven plugins and 3rd party dependencies are 
still not ready for Java 9
* some JVM options of current test build configurations require revision
* scala -- both 2.10 and 2.11 currently used in building and testing do not 
support Java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8379) Add maven-surefire-plugin support for PDS Compatibility tests

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8379:


 Summary: Add maven-surefire-plugin support for PDS Compatibility 
tests
 Key: IGNITE-8379
 URL: https://issues.apache.org/jira/browse/IGNITE-8379
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Peter Ivanov
 Fix For: 2.6


In continuation of the works on PDS Compatibility test suite, it is required to 
add support for {{maven-surefire-plugin}} in Compatibility Framework.
See IGNITE-8275 for details.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8316) Update RPM and DEB documentation

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8316:


 Summary: Update RPM and DEB documentation
 Key: IGNITE-8316
 URL: https://issues.apache.org/jira/browse/IGNITE-8316
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Peter Ivanov
 Fix For: 2.5


# Add DEB repository configuration and packages installation.
# Update RPM repository configuration and packages installation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8281) Add Docker image build for Apache Ignite Release

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8281:


 Summary: Add Docker image build for Apache Ignite Release
 Key: IGNITE-8281
 URL: https://issues.apache.org/jira/browse/IGNITE-8281
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Similar to Apache Ignite Nightly Release, add Docker images (Apache Ignite and 
WebConsole) build to Apache Ignite Release build. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8275) PDS (Compatibility): FoldersReuseCompatibilityTest

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8275:


 Summary: PDS (Compatibility): FoldersReuseCompatibilityTest
 Key: IGNITE-8275
 URL: https://issues.apache.org/jira/browse/IGNITE-8275
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Dmitriy Govorukhin


Some weird behaviour of *IgniteCompatibilityBasicTestSuite* test suite:
* {{mvn test}} run reports 8 successful tests (see 
https://ci.ignite.apache.org/viewLog.html?buildId=1211334&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_PdsCompatibility)
* {{mvn surefire:test}} run reports 2 failures (see 
https://ci.ignite.apache.org/viewLog.html?buildId=1211336&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_PdsCompatibility)
{code}
[2018-04-16 09:41:29,823][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: Directory [binary_meta, 
d0d49035_c611_4836_8956_8fdf220d7f46] is expected to exist 
[/data/teamcity/work/c182b70f2dfa6507/work/binary_meta/d0d49035_c611_4836_8956_8fdf220d7f46]
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:258)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:231)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:128)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_2(FoldersReuseCompatibilityTest.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
at java.lang.Thread.run(Thread.java:745)
[org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_2]
 junit.framework.AssertionFailedError: Directory [binary_meta, 
d0d49035_c611_4836_8956_8fdf220d7f46] is expected to exist 
[/data/teamcity/work/c182b70f2dfa6507/work/binary_meta/d0d49035_c611_4836_8956_8fdf220d7f46]
[org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_2]
 junit.framework.AssertionFailedError: Directory [binary_meta, 
d0d49035_c611_4836_8956_8fdf220d7f46] is expected to exist 
[/data/teamcity/work/c182b70f2dfa6507/work/binary_meta/d0d49035_c611_4836_8956_8fdf220d7f46]
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:258)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:231)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:128)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_2(FoldersReuseCompatibilityTest.java:97)
{code} 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Apache Ignite RPM packaging (Stage II)

[Peter Ivanov]

Current packages design (after installation) does not differ from binary
archive - everything works (except necessity to run service instead
ignite.sh) just the same way, including libs/optional.

Also, there can be issues with system JDK version by default, but every
problem will be in journalctl and/or  /var/log, and package has strong
dependency on any implementation of JDK 1.8.


I am lacking enough feedback about Apache Ignite from packages from real
users, don’t know real use cases so still "moving in the dark".


On Fri, 13 Apr 2018 at 22:18, Denis Magda  wrote:

> Ilya,
>
> Thanks for your inputs. The reason why we decided to split Ignite into
> several packages mimics the reason why Java community introduced modular
> subsystem for JDK. That's all about size. Ignite distribution is too big,
> and we're trying to separate it into several components so that people can
> install only the features they need.
>
> The point of a package is to ship something into root file system that can
> > be used from root file system. If cpp files require compilation we should
> > not ship them, or ship them to 'examples'. Ditto with benchmarks. If
> > there's no mechanism to add optional libs to Ignite classpath, we should
> > not ship optional libs. Moreover, some of 'optional' modules such as yarn
> > don't make sense here because they're not supposed to be used with
> > standalone Ignite.
>
>
> Agree that we need to ship the code that is ready to be run. As for the
> classpath thing, if an optional package is installed into the root (core)
> package directory, then its jars have to be added to "ignite/libs" folder.
> After that, the one needs to restart a cluster node, nd it will add the
> just installed optional libs to the classpath. *Petr*, does it work this
> way or can be implemented this way to address Ilya's concerns?
>
> --
> Denis
>
> On Fri, Apr 13, 2018 at 7:00 AM, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>
> wrote:
>
> > 2018-04-13 7:42 GMT+03:00 Peter Ivanov :
> >
> > > On Thu, 12 Apr 2018 at 20:04, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > >
> > > wrote:
> > >
> > > >
> > > > Moreover I did not find a way to start service if default installed
> JVM
> > > is
> > > > Java 7 :( I understand it's EOL, still this is something that hit me.
> > >
> > >
> > > Apache Ignite >=2.4 does not support Java 7 - it is said in
> > documentation,
> > > DEVNOTES and even in startup scripts.
> > >
> > >  I have Java 8 too, but I could not get service from package to start
> > Ignite since there's nowhere to put JAVA_HOME (or JVM_ARGS for that
> > matter). Is it possible to specify it while running packaged Ignite?
> >
> >
> > >
> > > >
> > > > apache-ignite-libs is a totally unexpected package name.
> apache-ignite
> > > core
> > > > doesn't depend on it. It doesn't enable anything out of the box. The
> > > > package is huge.
> > >
> > > ‘apache-ignite-libs’ is an aggregation package (for now) for all
> optional
> > > libs we are delivering. Possibly later they will be split more granular
> > or
> > > even package per lib (like php, perl, python, etc. do for their libs).
> > > This package dependency on ‘apache-ignite-core’ may seem confusing
> > though,
> > > I will try to explain it in IEP at least for current iteration.
> > >
> >
> > Okay, but how do you add optional libs to be included into Ignite
> classpath
> > while being launched by service? Is it even possible? If it isn't, I
> think
> > it doesn't make sense to ship apache-ignite-libs at all.
> >
> >
> > >
> > > Further naming may become clear when we’ll start initiative on
> including
> > > packages to popular Linux distributions and theirs community will join
> > > naming discussions.
> > >
> > Renaming packages once they're deployed widely will be a pain point to
> out
> > users. Some things should probably be thought out in advance.
> >
> >
> > >
> > >
> > >
> > > >
> > > > Frankly speaking, I'm not sure that improvements over Stage I are
> > enough
> > > as
> > > > of now. For demo-like activity, we can probably go with one package
> > fits
> > > > all.
> > > >
> > >
> > > The process of finding the best package architecture is iterative, but
>

Re: Apache Ignite RPM packaging (Stage II)

[Peter Ivanov]

On Thu, 12 Apr 2018 at 20:04, Ilya Kasnacheev 
wrote:

> Hello! I have tried your RPM scripts.
>
> First of all, I'm not sure that apache-ignite-core is a good name for
> package which contains the actual server node kit, and that apache-ignite
> is a good name for a package that will install everything (including cpp
> bindings). How does other packages solve this naming? I would go with
> apache-ignite and apache-ignite-full.


Previous package was named ‘apache-ignite’ and installed everything.
Current package is named ‘apache-ignite’ and installs everything (via
dependencies). I see convenience in this scheme.

‘apache-ignite-core’ name was selected because it is a core - minimum
required files to start the service. But I am open to suggestions
(-service, -node, etc.)



>
> Moreover I did not find a way to start service if default installed JVM is
> Java 7 :( I understand it's EOL, still this is something that hit me.


Apache Ignite >=2.4 does not support Java 7 - it is said in documentation,
DEVNOTES and even in startup scripts.



>
> apache-ignite-docs only contains scaladoc for scalar. Who would need a
> separate package for that? Why no javadocs? Maybe it's my build problem?


‘apache-ignite-docs’ contains both Javadoc and Scalardoc if sources were
built correctly



>
> apache-ignite-libs is a totally unexpected package name. apache-ignite core
> doesn't depend on it. It doesn't enable anything out of the box. The
> package is huge.


‘apache-ignite-libs’ is an aggregation package (for now) for all optional
libs we are delivering. Possibly later they will be split more granular or
even package per lib (like php, perl, python, etc. do for their libs).
This package dependency on ‘apache-ignite-core’ may seem confusing though,
I will try to explain it in IEP at least for current iteration.

Further naming may become clear when we’ll start initiative on including
packages to popular Linux distributions and theirs community will join
naming discussions.



>
> Frankly speaking, I'm not sure that improvements over Stage I are enough as
> of now. For demo-like activity, we can probably go with one package fits
> all.
>

The process of finding the best package architecture is iterative, but
previously community agreed in split design proposed for 2.5 release.

Also, split architecture is half of proposed improvements. The other half -
new process for deploying packages to Bintray (with virtually indefinite
storage capabilities).



>
> --
> Ilya Kasnacheev
>
> 2018-04-12 19:10 GMT+03:00 Petr Ivanov :
>
> > If someone from PMCы or Committers still sees necessity about including
> > these tasks into Apache Ignite 2.5 release, this is the last chance to do
> > so.
> > Otherwise this task will be moved to at 2.6 release at least, or even
> > moved to backlog indefinitely.
> >
> >
> >
> > > On 9 Apr 2018, at 19:08, Petr Ivanov  wrote:
> > >
> > > To top new RPM architecture off, update to release process is
> introduced
> > — [1] [2].
> > >
> > > Both tasks (this one and IGNITE-7647) are ready for review and should
> be
> > merged simultaneously.
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-8172
> > > [2] https://github.com/apache/ignite-release/pull/1
> > >
> > >
> > >
> > >
> > >> On 2 Apr 2018, at 18:22, Ilya Kasnacheev 
> > wrote:
> > >>
> > >> Hello!
> > >>
> > >> Let me share my idea of how this shoud work. Splitting package into
> > >> sub-packages should be dependency-driven.
> > >>
> > >> It means that all Ignite modules without dependencies or with small
> > >> dependencies (such as ignite-log4j) should be included in ignite-core.
> > It
> > >> doesn't make sense to make a zillion RPM packages.
> > >>
> > >> Critical things like ignite-spring and ignite-indexing should be in
> > >> ignite-core of course, even if they have dependencies. Ignite-core
> > should
> > >> be fully self-sufficient and feature-complete.
> > >>
> > >> However, e.g. .net API should probably be in a separate package,
> > because it
> > >> should depend on mono | net-core. We may also have ignite-devel
> package
> > >> which should include all modules which only make sense for developers
> > who
> > >> write code. Such as hibernate integration.
> > >>
> > >> I'm not sure about MR modules. The main question should be, does it
> have
> > >> dependencies? Can it run stand-alone without writing code?
> > >>
> > >> Hope this helps,
> > >>
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >> 2018-03-27 15:10 GMT+03:00 Petr Ivanov :
> > >>
> > >>> Hi, Igniters!
> > >>>
> > >>>
> > >>> Here are some news on our RPM packages initiative.
> > >>>
> > >>> 1. I’ve finished preliminary developing of Stage II version of RPM
> > >>> packages [1]. Main “new feature” is — split design. Also I’ve added
> > >>> package.sh script for automating package building process which will
> > help
> > >>> organise corresponding builds in TC as well as simplify process for
> > >>> developers who wishes to have custom packages.
> > >>> PR#370

[jira] [Created] (IGNITE-8222) Add docker image build for Nightly Release

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8222:


 Summary: Add docker image build for Nightly Release
 Key: IGNITE-8222
 URL: https://issues.apache.org/jira/browse/IGNITE-8222
 Project: Ignite
  Issue Type: New Feature
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# Create Meta-runner for Docker images building in TeamCity.
# Add new build on TeamCity which will build docker image from master.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8172) Update Apache Ignite's release scripts to match new RPM build and deploy architecture

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8172:


 Summary: Update Apache Ignite's release scripts to match new RPM 
build and deploy architecture
 Key: IGNITE-8172
 URL: https://issues.apache.org/jira/browse/IGNITE-8172
 Project: Ignite
  Issue Type: Improvement
  Components: build
Affects Versions: 2.4
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.5


# Implement new multi-package build scheme for RPM packages.
# Update release process: deploy RPM packages to {{ignite-rpm}} Bintray 
repository (with removal from Apache's Development Distribution SVN) instead of 
moving to ASF's release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8129) JDBC: JdbcThinConnectionSSLTest.testDefaultContext

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8129:


 Summary: JDBC: JdbcThinConnectionSSLTest.testDefaultContext
 Key: IGNITE-8129
 URL: https://issues.apache.org/jira/browse/IGNITE-8129
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Taras Ledkov


Test fails under strange conditions: it runs successful if is executed by {{mvn 
test}} command and fails if is executed by {{mvn surefire:test}}. Seems some 
maven reactor dependencies and/or race condition problems.
{code}
[2018-04-04 05:52:26,389][ERROR][main][root] Test failed.
java.sql.SQLException: Failed to SSL connect to server 
[url=jdbc:ignite:thin://127.0.0.1:10800]
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:93)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.connect(JdbcThinTcpIo.java:214)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:156)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.start(JdbcThinTcpIo.java:131)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.ensureConnected(JdbcThinConnection.java:156)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.(JdbcThinConnection.java:145)
at 
org.apache.ignite.IgniteJdbcThinDriver.connect(IgniteJdbcThinDriver.java:157)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:270)
at 
org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection 
during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
at 
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinSSLUtil.createSSLSocket(JdbcThinSSLUtil.java:88)
... 18 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
... 22 more
[08:54:52][org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext]
 java.sql.SQLException: Failed to SSL connect to server 
[url=jdbc:ignite:thin://127.0.0.1:10800]
[08:54:52]
[org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext] 
java.sql.SQLException: Failed to SSL connect to server 
[url=jdbc:ignite:thin://127.0.0.1:10800]
at 
org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection 
during handshake
at 
org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at 
org.apache.ignite.jdbc.thin.JdbcThinConnectionSSLTest.testDefaultContext(JdbcThinConnectionSSLTest.java:187)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Code inspection

[Peter Ivanov]

Anton, Dmitry is right.

We have to manually add condition when to consider build faulty based on
how many failed inspection are there.

For now I see this initiative as follows:
- find more or less correct set of inspections (there are lots of typos and
other irrelevant to code execution inspections) looking on the results of
core module build, as it has ~85% of target code;
- add all modules to composite project and setup schedule at least once a
week.


On Wed, 28 Mar 2018 at 19:09, Dmitry Pavlov  wrote:

> Inspection suites should be failed manually by some fail condition.
>
> This question will become actual in future. How to fail such suite on TC?
>
> ср, 28 мар. 2018 г. в 18:54, Anton Vinogradov :
>
> > Peter,
> >
> > Why 44 errors are green?
> >
> >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1145974&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_InspectionsAop
> >
> > 2018-03-28 16:27 GMT+03:00 Petr Ivanov :
> >
> > > After several problems, example run on Aleksey’s configuration is
> > > complete: https://ci.ignite.apache.org/viewLog.html?buildId=1164652 <
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1164652>
> > >
> > >
> > > > On 28 Mar 2018, at 10:28, Petr Ivanov  wrote:
> > > >
> > > > Started https://ci.ignite.apache.org/viewLog.html?buildId=1164002 <
> > > https://ci.ignite.apache.org/viewQueued.html?itemId=1163998> with
> > > Aleksey’s inspections profile.
> > > > Core (long) and AOP (short) modules will be tested as example.
> > > >
> > > >
> > > >
> > > >> On 27 Mar 2018, at 19:38, Dmitry Pavlov  >  > > dpavlov@gmail.com>> wrote:
> > > >>
> > > >> Hi Petr,
> > > >>
> > > >> Could you please take inspections and run it on AI code base in
> > > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > >
> IgniteTests24Java8_InspectionsCore&branch_IgniteTests24Java8=%3Cdefault%
> > > 3E&tab=buildTypeStatusDiv  > > viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore&branch_
> > > IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv>
> > > >> ?
> > > >>
> > > >> Sincerely,
> > > >> Dmitriy Pavlov
> > > >>
> > > >> вт, 27 мар. 2018 г. в 19:27, Dmitry Pavlov :
> > > >>
> > > >>> Alexey, thank you for bring this topic to top.
> > > >>>
> > > >>> What do you think about committing this inspections into Ignite
> code
> > > base?
> > > >>>
> > > >>> What can be our next steps after demonstrating CI check is possible
> > > >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > >
> IgniteTests24Java8_InspectionsCore&branch_IgniteTests24Java8=%3Cdefault%
> > > 3E&tab=buildTypeStatusDiv
> > > >>> ?
> > > >>>
> > > >>> Sincerely,
> > > >>> Dmitriy Pavlov
> > > >>>
> > > >>> вт, 27 мар. 2018 г. в 15:28, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com
> > >  :
> > > >>>
> > >  Bumping up.
> > > 
> > >  Attached is my local inspections profile exported from Idea. Let's
> > run
> > >  the first iteration and check if it differs significantly from
> other
> > >  community members.
> > > 
> > >  --AG
> > > 
> > >  2018-03-19 16:39 GMT+03:00 Petr Ivanov :
> > > 
> > > > Filed https://issues.apache.org/jira/browse/IGNITE-7985 <
> > > > https://issues.apache.org/jira/browse/IGNITE-7985> [1].
> > > 
> > > 
> > > >
> > > >
> > > >
> > > >> On 18 Mar 2018, at 00:56, Dmitry Pavlov 
> > > wrote:
> > > >>
> > > >> Hello Petr,
> > > >>
> > > >> Many members of the community would appreciate such additional
> > code
> > > > control, and it's a pity that no one made this happen. Agree?
> > > >>
> > > >> Could you please pick up this activity?
> > > >>
> > > >> It might be an idea to create 'IDEA Inspections' step to be run
> in
> > > > parallel with 'Build Apache Ignite'. WDYT? Would it work?
> > > >>
> > > >> Sincerely,
> > > >> Dmitriy Pavlov
> > > >>
> > > >
> > > > https://confluence.jetbrains.com/display/TCD10/Inspections <
> > > > https://confluence.jetbrains.com/display/TCD10/Inspections>
> > > >>
> > > >>
> > > >> пн, 12 мар. 2018 г. в 14:37, Dmitry Pavlov <
> dpavlov@gmail.com
> > > > >:
> > > 
> > > 
> > > >> Hi Dmitriy,
> > > >>
> > > >> would you pick up this activity?
> > > >>
> > > >> Sincerely,
> > > >> Dmitriy Pavlov
> > > >>
> > > >
> > > > вт, 6 мар. 2018 г. в 14:09, Dmitry Pavlov  > > > >:
> > > 
> > > 
> > > >> What I can suggest now it is to take XML file with existing as
> is
> > > from
> > > > previous topic (I remember someone in community already prepared
> > > settings)
> > > > and set up TeamCity Run configuration as part of Run All Basic
> > Tests
> > > (per
> > > > commit basis).
> > > >>
> > > >> If we don’t have XML, I suggest to enable build-in Idea
> > inspections
> > > > 'as is' on TeamCity and

Re: What's about releasing Ignite 2.5 a bit earlier?

[Peter Ivanov]

My concern is only in fact, that Ignite is currently not tested under
Java9/10 as thorough as it is under Java8.

As I mentioned before - I agree with no blocker on this matter and have no
other problems to report for now. I guess I’ll start a new thread about the
scheme of supporting future Java versions.


On Sat, 24 Mar 2018 at 07:29, Denis Magda  wrote:

> Petr,
>
> I think your statement in regards the non-readiness for the production
> usage is too strong :) The issue you listed treated as usability ones by
> me. Agree that it's inconvenient to inject ‘--add-modules’ here and there
> but it doesn't lead to failures at runtime.
>
> If I'm still missing something and there are the bugs that might affect the
> stability of the clusters at runtime, then please share them with us.
> You're more aware than anyone else.
>
> --
> Denis
>
> On Fri, Mar 23, 2018 at 8:50 PM, Petr Ivanov  wrote:
>
> > Agree with no blocker.
> >
> > Then as developers we just have to send a clear message that "we making
> it
> > towards Java9/10 honest support, but do not use it yet on prod
> > environments” :)
> >
> >
> > > On 23 Mar 2018, at 22:41, Denis Magda  wrote:
> > >
> > > Petr,
> > >
> > > I guess we would need much more time to handle all Java 9/10 tasks.
> Since
> > > none of them looks like a blocker to me, I would suggest us not to rush
> > and
> > > target the tasks for 2.4 release.
> > >
> > > Overall, I see that we're in an agreement in regards the earlier date
> of
> > > 2.5 release. I'll let the rest of the community to speak out until the
> > > beginning of the next week.
> > >
> > > --
> > > Denis
> > >
> > >
> > >
> > > On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov 
> > wrote:
> > >
> > >> I’ll do my best to deliver packages in time.
> > >>
> > >>
> > >> Concerning Java 9/10 — AFAIK there are limitations how do we support
> it:
> > >> * compilation is supported with scala_2.10 modules switched off (due
> to
> > >> scala support Java 9 itself starting from 2.12.x+ versions);
> > >> * also compilation and run is possible only with lots of
> ‘--add-modules’
> > >> hacks — I think that to say we support Java 9 we have to add modules
> > info
> > >> to every package;
> > >> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention,
> > >> because there are some problems with theirs run.
> > >>
> > >>
> > >>
> > >>> On 22 Mar 2018, at 21:09, Denis Magda  wrote:
> > >>>
> > >>> Petr,
> > >>>
> > >>> Java Thin client, GA Grid, COPY command are the most significant
> > >> additions
> > >>> to the release (if to talk about the features). Aside from that, I
> see
> > >> many
> > >>> valuable optimizations and fixes that have been sitting in the master
> > >> for a
> > >>> while (some of them were merged in January). It's preferable to
> release
> > >>> them.
> > >>>
> > >>> As for Java 10 and DEB, if you feel you can't make them to the
> release,
> > >>> then it can wait till 2.6.
> > >>>
> > >>> Speaking of Java 9, what's left? I thought it's already fully
> > supported.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov 
> > >> wrote:
> > >>>
> >  Will there be a major new feature or this release will concentrate
> on
> >  stability and optimisations?
> > 
> >  Also, I guess, we will have to include into 2.5 release full support
> > for
> >  Java 9 and Java 10 (that WILL require some developers time).
> >  And RPM / DEB packages stage II phase will require lots of testing
> and
> >  infrastructure preparations: place to store package, RPM / DEB build
> >  inclusion into release process and so on.
> > 
> >  Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all
> > >> those
> >  activities are not finished in time.
> > 
> > 
> > 
> > > On 22 Mar 2018, at 20:39, Denis Magda  wrote:
> > >
> > > Igniters,
> > >
> > > According to our regular schedule, every new Ignite version usually
> > >> goes
> > > public once in 3 months. As you remember, the latest 2.4 release,
> > which
> > > took us 5 months to improve and roll out, was based on the version
> of
> > >> the
> > > source code dated by January.
> > >
> > > Since that time the master branch went far ahead and already
> > >> incorporates
> > > many valuable fixes and capabilities such as:
> > >
> > > - Fixes provided as a part of "Gree Team City" activity.
> > > - Persistence: page replacement algorithm and throttling
> > >> optimizations,
> > > out of memory in checkpointing buffer corrections, etc. Alex G and
> >  Ivan can
> > > shed more light here.
> > > - Data loading optimizations for SQL: streaming for JDBC thin
> driver
> >  and
> > > copy command
> > > - Genetic Algorithms Grid Contribution!
> > > - Java Thin Client developed by Alexey Kukushkin
> > >
> > >
> > > - the list goes on and on... Please share the contributions you are
> > >

[jira] [Created] (IGNITE-8003) Dead documentation interface element

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8003:


 Summary: Dead documentation interface element
 Key: IGNITE-8003
 URL: https://issues.apache.org/jira/browse/IGNITE-8003
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.4
Reporter: Peter Ivanov
Assignee: Prachi Garg
 Attachments: Screen_Shot_2018_03_15_at_11_43_07.png

Most of the tables in lists of artifacts (for example on Downloads page) have 
strange interface element settling down to the right, which does nothing (see 
[^Screen_Shot_2018_03_15_at_11_43_07.png]).

I guess it should be either removed or fixed, whatever designation it has.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7985) Integration JetBrains IntelliJ IDEA code inspections as TC build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7985:


 Summary: Integration JetBrains IntelliJ IDEA code inspections as 
TC build
 Key: IGNITE-7985
 URL: https://issues.apache.org/jira/browse/IGNITE-7985
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


https://confluence.jetbrains.com/display/TCD10/Inspections



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7945) Apache Ignite nightly releases

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7945:


 Summary: Apache Ignite nightly releases
 Key: IGNITE-7945
 URL: https://issues.apache.org/jira/browse/IGNITE-7945
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# As discussed 
[here|http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-nightly-release-builds-td27966.html],
 it is necessary to prepare build on [AI TeamCity|ttps://ci.ignite.apache.org] 
which will run every night and will build release binaries for *{{master}}* 
branch.
# Prepare corresponding [Apache Ignite 
Documentation|https://ignite.apache.org/download.cgi] section for link to 
latest nightly release binaries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7937) Move Apache Ignite 2.4+ Java 8 tests to Single Build architecture

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7937:


 Summary: Move Apache Ignite 2.4+ Java 8 tests to Single Build 
architecture
 Key: IGNITE-7937
 URL: https://issues.apache.org/jira/browse/IGNITE-7937
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# Use working example from [\[Not for production use\] Ignite Tests 2.0+ (Java 
8/9)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests20Java89] 
project.
# Start with green tests suites.
# Revise _templates_ and _VSC roots_.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7821) Update Apache Ignite and Web Console Dockerfile for 2.4 version and local build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7821:


 Summary: Update Apache Ignite and Web Console Dockerfile for 2.4 
version and local build
 Key: IGNITE-7821
 URL: https://issues.apache.org/jira/browse/IGNITE-7821
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.4


# Update Dockerfiles in order to match upcoming 2.4 release.
# Change Apache Ignite's Dockerfile to get binaries from local build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7808) Automate Docker images build

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7808:


 Summary: Automate Docker images build
 Key: IGNITE-7808
 URL: https://issues.apache.org/jira/browse/IGNITE-7808
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Introduce and document process and tools for automated Docked images build 
based on release tag. Include both Ignite and Web Console images.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7697) Update maven-javadoc-plugin version

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7697:


 Summary: Update maven-javadoc-plugin version
 Key: IGNITE-7697
 URL: https://issues.apache.org/jira/browse/IGNITE-7697
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.4
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.5


Update version of {{maven-javadoc-plugin}} in order to try to overcome 
following error:
{code}
javadoc: warning - Error fetching URL: 
http://hadoop.apache.org/docs/current/api/
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7672) Fix Javadoc in Java 8

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7672:


 Summary: Fix Javadoc in Java 8
 Key: IGNITE-7672
 URL: https://issues.apache.org/jira/browse/IGNITE-7672
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.4
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.5


Currently, Javadoc builds on TC with {{-Xdoclint:none}} option enabled, that 
turns off Java 8's new Javadoc check algorithm. Natively we have lots of 
warnings and errors in master branch.
# Create per-module tasks (with inclusion to this one) for receiving scope of 
debt.
# Create corresponding build on TC for testing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7671) Fix .gitignore files are tracked error

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7671:


 Summary: Fix .gitignore files are tracked error
 Key: IGNITE-7671
 URL: https://issues.apache.org/jira/browse/IGNITE-7671
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Current {{.gitignore}} has definitions of files to ignore, which are already 
under the version control system (some *.sh scripts for example). It needs to 
be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7647) Apache Ignite RPM packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7647:


 Summary: Apache Ignite RPM packages
 Key: IGNITE-7647
 URL: https://issues.apache.org/jira/browse/IGNITE-7647
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Repack RPM specification to:
* be able to build package from source code
* divide single package into multiple packages (core + optional).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7646:


 Summary: OSGI tests fail to unlock build directory causing 
following builds to fail to start
 Key: IGNITE-7646
 URL: https://issues.apache.org/jira/browse/IGNITE-7646
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov


After running test suite [Ignite Tests 2.4+ \[Java 8\] Ignite 
OSGi|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteOSGi]
 under Windows based agent, following builds fail to start with error
{code}
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle1\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle2\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle3\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle4\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle5\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle6\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle7\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle8\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\cache.lock
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\log\karaf.log
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.diagnostic.boot-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.jaas.boot-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.main-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.osgi.core-6.0.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\javax.annotation-api-1.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.karaf.exception-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-2.7.2_2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.activation-api-1.1-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxb-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxp-api-1.4-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxws-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.saaj-api-1.3-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work

[jira] [Created] (IGNITE-7625) Fix links for Javadoc

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7625:


 Summary: Fix links for Javadoc
 Key: IGNITE-7625
 URL: https://issues.apache.org/jira/browse/IGNITE-7625
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


# {{/parent/pom.xml}}
Remove obsolete linking to http://docs.oracle.com/javase/7/docs/api/ -- linking 
to corresponding JavaSe documentation is automatic due to {{detectJavaApiLink}} 
flag of {{maven-javadoc-plugin}} set in {{true}} by default.
# {{/modules/yarn/src/main/java/org/apache/ignite/yarn/IgniteProvider.java}}
Fix direct link to {{Logger.java}} Javadoc documentation.
{code}
 * Please take a look at http://docs.oracle.com/javase/7/docs/api/java/util/logging/Logger.html";>Logger
 javadoc
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7621) Review current builds on TeamCity

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7621:


 Summary: Review current builds on TeamCity
 Key: IGNITE-7621
 URL: https://issues.apache.org/jira/browse/IGNITE-7621
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


There is a little under 600 builds currently configured on teamcity. It is 
required to review each of them and:
* revise and clean obsolete build plans
* revise and clean duplicated VCS roots
* revise and reconfigure corresponding triggers
* revise and strict build configuration access permissions
* document everything



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7550) Fix windows *.bat scripts Java 9 compatibility

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7550:


 Summary: Fix windows *.bat scripts Java 9 compatibility
 Key: IGNITE-7550
 URL: https://issues.apache.org/jira/browse/IGNITE-7550
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Additional check revealed errors and remarks in \{{ignitevisorcmd.bat}}, 
\{{control.bat}} and \{{ignite.bat}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7543) Rename KEYS.txt

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7543:


 Summary: Rename KEYS.txt
 Key: IGNITE-7543
 URL: https://issues.apache.org/jira/browse/IGNITE-7543
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Anton Vinogradov


Since IGNITE-7107, http://apache.org/dist/ignite/KEYS.txt will be used also for 
GPG repository check, it is desirable to rename {{KEYS.txt}} to {{KEYS}} for 
more convenient usage (like Cassandra has: http://apache.org/dist/cassandra/)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7538) Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7538:


 Summary: Introduce new test project for Ignite 2.0+ with Java 8 / 
Java 9 compatibility
 Key: IGNITE-7538
 URL: https://issues.apache.org/jira/browse/IGNITE-7538
 Project: Ignite
  Issue Type: Sub-task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI 
which meet the problem of test configuration synchronization. It is necessary 
to devise a solution for overcoming this issue.

Possible approaches:
# Single project for tests with run with different parameters.
Problems:
#* Test History will show history for all builds with any parameters 
combination.
#* Mute test will mute test for all parameters configuration.
# Several project (differentiated by parameter) with build configuration 
synchronisation automation.
Problems:
#* Maintainability — how to seamlessly support build configuration 
synchronisation.

Research for both approaches must be held.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7393) Apache Ignite delivery in RPM / DEV packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7393:


 Summary: Apache Ignite delivery in RPM / DEV packages
 Key: IGNITE-7393
 URL: https://issues.apache.org/jira/browse/IGNITE-7393
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
Priority: Critical
 Fix For: 2.5


Aggregation task for first stage of preparing Apache Ignite delivery through 
RPM / DEB packages.
Steps:
# Prepare source-based package build procedures for RPM and DEB.
# Introduce these build procedures to Release Apache Ignite task in PublicTC 
(including generation of RPM / DEB repositories structure for deployment to 
apache.org/dist).
# Introduce PPA DEB repository for Apache Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7326) Fix ignitevisorcmd | sqlline scripts to be able to run from /usr/bin installed as symbolic links

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7326:


 Summary: Fix ignitevisorcmd | sqlline scripts to be able to run 
from /usr/bin installed as symbolic links
 Key: IGNITE-7326
 URL: https://issues.apache.org/jira/browse/IGNITE-7326
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.5


Currenlty, {{ignitevisorcmd.sh}} and {{sqlline.sh}} being installed into 
{{/usr/bin}} will fail to run because of:
* their unawarelessness of theirs real location;
* necessity to write to {{$\{IGNITE_HOME}/work}} which can have different 
permissions and owner (in packages, for example).

It is required to rewrite these scripts to be able to run from anywhere by 
theirs symbolic linka and with some temporary dir ({{/tmp}} for example) as 
workdir.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7190) Docker Hub official repository deployment

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7190:


 Summary: Docker Hub official repository deployment
 Key: IGNITE-7190
 URL: https://issues.apache.org/jira/browse/IGNITE-7190
 Project: Ignite
  Issue Type: New Feature
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Research possibility to integrate into Official Docker Hub Repositories.
Use 
https://docs.docker.com/docker-hub/official_repos/#how-do-i-create-a-new-official-repository
 as start.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7144) Java 9: fix build issue with tools.jar not found

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7144:


 Summary: Java 9: fix build issue with tools.jar not found
 Key: IGNITE-7144
 URL: https://issues.apache.org/jira/browse/IGNITE-7144
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


{code}
[ERROR] Failed to execute goal on project ignite-tools: Could not resolve 
dependencies for project org.apache.ignite:ignite-tools:jar:2.4.0-SNAPSHOT: 
Could not find artifact com.sun:tools:jar:9.0.1 at specified path 
/Library/Java/JavaVirtualMachines/jdk-9.0.1.jdk/Contents/Home/../lib/tools.jar
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7142) Introduce ability to run Ignite Tests on TeamCity with Java 9

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7142:


 Summary: Introduce ability to run Ignite Tests on TeamCity with 
Java 9
 Key: IGNITE-7142
 URL: https://issues.apache.org/jira/browse/IGNITE-7142
 Project: Ignite
  Issue Type: New Feature
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Introduce ability to run Ignite Tests on TeamCity with Java 9 (and Java 1.8 as 
well).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7108) Apache Ignite DEB packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7108:


 Summary: Apache Ignite DEB packages
 Key: IGNITE-7108
 URL: https://issues.apache.org/jira/browse/IGNITE-7108
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
 Fix For: 2.4


Pack apache-ignite into DEB package for distribution through DEB-based Linux 
distros (Ubuntu / Debian, etc.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7107) Apache Ignite RPM packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7107:


 Summary: Apache Ignite RPM packages
 Key: IGNITE-7107
 URL: https://issues.apache.org/jira/browse/IGNITE-7107
 Project: Ignite
  Issue Type: Improvement
  Components: binary
Reporter: Peter Ivanov
 Fix For: 2.4


Pack apache-ignite into RPM package for distribution through RPM-based Linux 
distros (Fedora / CentOS / RHEL, etc.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)