Igniters,
Currently, we have three separate modules for Ignite Spring Data
integrations - [1 - 3]. Each of them depends on the specific version of
the Spring Data - 1.0, 2.0, and 2.2, respectively.
I propose to:
1. remove extension modules that are tied to the specific Spring Data
versions
Hello, Maxim.
Thanks for investigation!
> 4. log4j-test.xml, tests.properties these files from the ignite-core module
> required to run tests and it seems they should be shared between projects
> also as tests resources.
As you may see most copies of these files are empty.
I think we should mo
Hello Igniters,
We have a lot of Ignite extensions waiting to be released (e.g. aws,
gce, topology-validator, ignite-spring-tx-ext etc.). I think it is a
good point in time to make some kind of automation and simplify our
release process for Ignite extension modules removing manual steps
from it.
Agree with it, it is consistent. Seems that I have suggested the same
чт, 17 февр. 2022 г., 11:05 Pavel Tupitsyn :
> I've reviewed the code again and it does not seem right to override
> user-defined heartbeat interval with a *bigger* value,
> so now I only set it to 1/3 of idleTimeout when the u
I've reviewed the code again and it does not seem right to override
user-defined heartbeat interval with a *bigger* value,
so now I only set it to 1/3 of idleTimeout when the user-specified value is
not already less than that.
On Wed, Feb 16, 2022 at 7:19 PM Pavel Tupitsyn wrote:
> Ok, let's kee
