Igor, Raul and Anton.
As far as I remember we decided to have version in each module pom because
of some problem with maven release.
So, we ALSO NEED CHECK RELEASE PROCEDURE and see will new approach work or
not.
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Ok, in case of using version & release plugins it's better just to reuse
parent project version in all modules, as you previously mentioned.
Thus the main question is - if there are any specific cases for using "1"
as a version number in parent POM? Cause such versioning schema also
doesn't allow
Hi；
ignite.message() method cannot work in async mode,withAsync() method is
invalid,is it ok or is a bug?
I disagree. It's all about using the tools for the job in the way they were
intended to.
As I said, your approach does not allow us to (1) release the Ignite Parent
POM, (2) use the version plugin, (3) use the release plugin.
Moreover, your argument about copy-paste does not sustain. Because you
Valentin Kulichenko created IGNITE-3710:
---
Summary: Upgrade ignite-spark module to Spark 2.0
Key: IGNITE-3710
URL: https://issues.apache.org/jira/browse/IGNITE-3710
Project: Ignite
Issue
Anton,
I executed tests for my pull request and here are the results:
http://149.202.210.143:8111/viewLog.html?buildId=301277&tab=buildResultsDiv&buildTypeId=IgniteTests_RunAll
It looks like there are some problems with *Snapshot dependecy*, but it's
not only specific to my pull request, but to d
Well, it's all about how to minimize copy-pasting parent version to
constantly growing amount of module POMs while switching to development of
new version.
Following your example with:
*mvn clean install -Dapp.version=12893123*
It looks like if somebody doing such things - he is likely doing it
Pavel Tupitsyn created IGNITE-3709:
--
Summary: .NET: Support primitive type names in QueryEntity
Key: IGNITE-3709
URL: https://issues.apache.org/jira/browse/IGNITE-3709
Project: Ignite
Issue
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/970
Ignite-2560
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2560
Alternatively you can review and apply these
1. Agree. You can use org.apache.ignite.internal.GridPerformanceSuggestions
to print this warning.
2. Disagree. For me this brings a lot of confusion.
Alex, can you please check that all internal caches used in Ignite
internals have this property set to false.
--Yakov
2016-08-18 17:24 GMT+03:00
Github user ntikhonov closed the pull request at:
https://github.com/apache/ignite/pull/951
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user ntikhonov closed the pull request at:
https://github.com/apache/ignite/pull/955
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user pperalta closed the pull request at:
https://github.com/apache/ignite/pull/952
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/672
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/969
IGNITE-3632 IGFS: Use task execution for PARTITIONED cache when metadata
is co-located and current node is not affinity node.
You can merge this pull request into a Git repository by run
Guys,
Currently Ignite tries to be compatible with JSR-107 specification which is
"store-by-value" by default.
So we have the copyOnRead flag with default value set to true in
CacheConfiguration.
The truth is the performance of Ignite with this flag disabled is
significantly better.
With a simpl
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/946
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/966
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/968
Ignite-3698: ODBC: LEN(string) function
...is implemented
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3698
Hi Igor,
Unfortunately the ${app.version} approach does not play well with the Maven
ecosystem. The Maven release and versions plugins don't know to go into an
arbitrary property to bump up the version number.
The goal with inlining the parent version numbers is to have a solid,
traceable and aut
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/967
IGNITE-3694
IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testAppendConsistencyMultithreaded
hangs
You can merge this pull request into a Git repository by running:
$ git pull https
Alexey Kuznetsov created IGNITE-3708:
Summary: MySQLDialect.loadCacheSelectRangeQuery return statement
that actually not supported by MySQL
Key: IGNITE-3708
URL: https://issues.apache.org/jira/browse/IGNITE-37
Ksenia Rybakova created IGNITE-3707:
---
Summary: Throughput drops to 0 during failover test when killed
node returns to the grid
Key: IGNITE-3707
URL: https://issues.apache.org/jira/browse/IGNITE-3707
Hi all,
1) To run your pull request click "..." to the right of "Run" and chose
Changes -> Default Branch -> pull/961/head
2) Parent pom version is 1 because it was stable solution while project
grew extremely fast.
I see no restrictions to change it, but we have to theck it works, twice.
We need
24 matches
Mail list logo
