GitHub user vveider opened a pull request:
https://github.com/apache/ignite-release/pull/3
IGNITE-7251 Remove term "fabric" from Ignite deliverables
* modified scripts to comply with "fabric" removal
You can merge this pull request into a Git repository by runn
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/4804
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4889
IGNITE-7251 Remove term "fabric" from Ignite deliverables
* removed additional "fabric" inclusion
You can merge this pull request into a Git repository by running:
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4945
IGNITE-9685 [ML] Add ignite-tensorflow module to build artifacts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4951
IGNITE-9583 PHP thin: php directory should be included in binary release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/5014
IGNITE-9918 Default configuration missed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9918
Alternatively you
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/5015
IGNITE-9922 Python thin: python directory should be included in binarâ¦
â¦y release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
ASC / SHA512 verification:
1. Download signing key: wget -c https://www.apache.org/dist/ignite/KEYS
2. Import key: gpg --import KEYS
3. Download release with signature and sha512 hash sum: wget -c
http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip
http://apache.org/dist/ignite/2.7.0/a
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3969
Ignite 8457
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8457
Alternatively you can review and apply these
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3969
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3970
IGNITE-8441 Java 9 (Stage II)
* updated some dependencies version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3989
IGNITE-8478 SqlLine run failure on Java 9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8478
Alternatively
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4005
IGNITE-8510 RPM package 2.4.0 is incorrectly upgraded by 2.5.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4013
IGNITE-8520 ignite-gce/ignite-shmem is redundant
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8520
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4017
IGNITE-8461 Scala-2.10 modules compilation failure under JDK 9
* fixed Scala 2.10 compilation on JDK9
* updated other Scala versions
You can merge this pull request into a Git repository by
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4038
IGNITE-8526 Create web-agent docker image for k8s deployment
* added web-agent separate docker image build
* refactored and unified docker specifications layout
You can merge this pull
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4056
IGNITE-8586 Minor fix for Apache Ignite's release procedure
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4194
IGNITE-8804 Windows WSL configuration has to be added to Ignite configs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4195
IGNITE-8807 Apache Ignite Linux packages 2.6 update
* update packages' version to 2.6.0
* added dirmngr dependency for DEB package for Debian apt-key
network compatibility
You can
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4438
IGNITE-9089 Web Agent not starting in docker container.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9089
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4439
IGNITE-9030 Apache Ignite 2.7 Linux packages version update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9030
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3315
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4771
Ignite 8454
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8454
Alternatively you can review and apply these
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4804
IGNITE-7251 Remove term "fabric" from Ignite deliverables
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
Hi, Denis.
https://issues.apache.org/jira/browse/IGNITE-7107
https://issues.apache.org/jira/browse/IGNITE-7108
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3171
IGNITE-7107 Apache Ignite RPM packages
* added spec for RPM build
* added instructions to DEVNOTES.txt
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3172
IGNITE-7144 Java 9: fix build issue with tools.jar not found
* added profiles to parent and ignite-tools modules to detect java-9
environment and run parametrised build
* added macOS
I've added IEP document [1] with current packages design for overview.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-11%3A+Introduce+Apache+Ignite+delivery+in+RPM+and+DEB+packages
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Got task IGNITE-7209. Started work on switching to java-1.8.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3235
IGNITE-7190 Docker Hub official repository deployment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7190
Prepared pull request to apache/ignite [1] with changes to meet the Docker
Hub requirements (best practices and other stuff).
Looking forward to see it in master ASAP to continue my work and prepare PRs
to Docker Hub's repositories.
[1] https://github.com/apache/ignite/pull/3235
--
Sent from:
Very good. I came to the same thoughts.
Yet, there is a situation that some classes in *.java.* and .*java8.*
packages that share the name and policy of merging them is not quite clear.
Should *.java.* classes be replace by .*java8.*?
--
Sent from: http://apache-ignite-developers.2346864.n4.nab
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3240
IGNITE-7203 Java 8 by default
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7203
Alternatively you can review
Hi, Denis!
Can you be a little bit more specific about "fabric" mentions? What exactly
should be renamed?
Package has final name "apache-ignite-fabric" in order to follow the
convention of upstream source naming and DEVNOTES.txt instructions just name
files as they are.
--
Sent from: http://apa
Done. See updated PR#3171 [1]
[1] https://github.com/apache/ignite/pull/3171
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Ilya Kasnacheev wrote
> I have noticed that both spec and DEVNOTES are made to use tabs alongside
> with spaces. I thought we are avoiding tabs? Please confirm that usage of
> tabs is desired in this case.
My fault - got used to editing such files in default vim. Fixed and updated
vim settings to
I've ran some tests for Java 8 implementation comparison and need help of
fellow igniters to look through the results. Run report follows.
Branch: [1]
Master: [2]
Problem tests:
1. Branch
1. _Licenses & Javadoc — failed
2. Ignite Basic — execution timed out
3. Ignite Basic 2 — executi
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3172
---
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3171
---
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3240
---
GitHub user vveider reopened a pull request:
https://github.com/apache/ignite/pull/3240
IGNITE-7203 Java 8 by default
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7203
Alternatively you can
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3315
IGNITE-7251 Remove term "fabric" from Ignite deliverables
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite i
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3348
IGNITE-7203 Java 8 by default
* further improved AOP test behaviour by moving javaagent call into pom.xml
.NET: Fix WindowsServiceTest - pass JVM path to the service
.NET: Another attempt
Hi, Igniters!
While working on Java 9 support adaptation, came to a problem with scala
2.10 and corresponding modules (scala-2.10, spark-2.10 and
visor-console-2.10) which will not compile under Java 9. As I see here [1]
scala 2.10 is already deprecated in spark 2.1.0 (and lately spark version
up
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3357
Ignite 6730
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6730
Alternatively you can review and apply these
Github user vveider closed the pull request at:
https://github.com/apache/ignite/pull/3348
---
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3396
IGNITE-7107 Apache Ignite RPM packages
* added changelog to package specification
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Hi, all!
I'm glad to announce that official Java 8 support finally found its way into
Apache Ignite's master and, respectively, 2.4 release!
What does it mean for contributors?
1. Java 7 support is dropped, compilation and run is impossible.
2. Tests on Public TC should be run on "Ignite Tests 2
Hi, Igniters!
Ticket IGNITE-6730 [1] was merged to master (and ignite-2.4) and now we have
preliminary support of Java 9, which includes:
- compilation with JDK9 with some constraints (scala-2.10 based modules
should be turned off)
- run with JRE9/JDK9 through default scripts (ignite.{sh|bat})
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3441
IGNITE-7550 Fix windows *.bat scripts Java 9 compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7550
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3446
IGNITE-7534 ClusterGroupExample duplicate
* removed
examples/src/main/java/org/apache/ignite/examples/computegrid/cluster
You can merge this pull request into a Git repository by running
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3450
IGNITE-898: Fixed error when path to Ignite folder contains whitespaces
* Fixed error when path to ignite folder contains whitespaces
* Fixed error when path to ignite folder contains
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3473
IGNITE-7625 Fix links for Javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7625
Alternatively you can
Hi, Igniters.
Found (and marked obsolete) several build project on our CI server:
* [Obsolete] Assembly and Release [1] - previous release project on Java 7.
* [Obsolete] Ignite JDK compatibility [2] - project that did not run for 2
years.
* [Obsolete] Ignite Release [3] - more previous release p
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3482
IGNITE-7538 Introduce new test project for Ignite 2.0+ with Java 8 / Java 9
compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3520
IGNITE-7697 Update maven-javadoc-plugin version
* updated maven-javadoc-plugin version
* added maven-javadoc-plugin version override to ignite-apache-license-gen
* updated flatten-maven
Nikolay, I raised your permissions to Ignite Committer status.
Check it out, please.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3574
IGNITE-7821 Update Apache Ignite and Web Console Dockerfile for 2.4 version
and local build
* removed Apache Ignite's Docker module obsolete autobuild directory layout
* updated A
Hi, Igniters!
In order to correctly process Apache Ignite 2.4 release, I've implemented
several changes in Apache Ignite's and Web Console's docker build procedure
[1].
My main motivation was to:
1. Unify approach to docker image architecture. Previously, Apache Ignite
docker image build procedur
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3625
Ignite wc 157
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-wc-157
Alternatively you can review and apply
Hi, Igniters!
I suggest we continue our discussion concerning Apache Ignite nightly
release builds.
I'd like to prepare one on our CI server (TeamCity) and will be glad to hear
wishes and proposal about this project.
Currently, I see it as scheduled build which builds release binaries from
maste
Hi, Igniters!
Release 2.4 is almost there, at least binary part of it, so I'd like to move
forward to further improve and widen AI delivery through packages.
As of now, Apache Ignite ships in RPM package weighing about 280M+ and, to
improve usability and significantly reduce required download siz
Prepared corresponding task [1], will start preparing build in the nearest
future.
[1] https://issues.apache.org/jira/browse/IGNITE-7945
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi, all!
Does anyone know what is this button with arrow and disk at the right corner
of versions list header? [1]
Seems that it does nothing.
[1] https://ibb.co/eJf5uc
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi, Igniters!
Took the liberty to introduce minor refactoring into test build names in our
(now) main test project Ignite Tests 2.4+ (Java 8) [1]
Changes affected the numeration of tests with common name, i.e
Ignite Basic => Ignite Basic [I]
Ignite Basic 2 => Ignite Basic [II]
And so on.
+1 to sticking to one suite for now.
Maybe someday when examples' tests will surpass adequate build time, we'll
consider splitting them.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Igniters,
As you may noticed, main test project is undergoing some refactoring;
namely, we are moving to architecture which is designed to reduce full tests
run time by introducing 'single-build / multiple tests' scheme: Apache
Ignite is built once and its artifacts are used in later parallel tes
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3703
IGNITE-7647
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7647
Alternatively you can review and apply these
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3710
IGNITE-7985 Integration JetBrains IntelliJ IDEA code inspections as Tâ¦
â¦C build
* added inspections.xml from Goncharuk A.
You can merge this pull request into a Git repository by
GitHub user vveider opened a pull request:
https://github.com/apache/ignite-release/pull/1
IGNITE-8172
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vveider/ignite-release ignite-8172
Alternatively you can review and apply
Github user vveider commented on a diff in the pull request:
https://github.com/apache/ignite-release/pull/1#discussion_r180753764
--- Diff: scripts/vote_3_step_1[rpm]create_repository.sh ---
@@ -19,17 +27,19 @@ then
fi
echo
+
#
# Build package
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3869
IGNITE-7108 Apache Ignite 2.5 RPM and DEB packages
* added package.sh script for automation DEB and RPM packages build
* added DEB package build
* updated RPM package version to 2.5.0
72 matches
Mail list logo
