PR [0] was updated. Scope of Ignite and
dependencies has been set to "provided".
Could someone take a look, please?
[0] - https://github.com/apache/ignite-extensions/pull/28
On 12.11.2020 11:53, Alexey Goncharuk wrote:
Yes, the idea is correct. I cannot vouch for the ignite-spring-data
Yes, the idea is correct. I cannot vouch for the ignite-spring-data
extension because I do not know whether there are maintenance releases for
each of the sprint-data-[2.0, 2.1, 2.2] streams. If spring-data-2.0.x is no
longer supported, then definitely we should be good to release it once and
move
Alexey,
Did I understand you correctly?
For each new version of any extension, the minimum Ignite version and
the minimum version of will be explicitly specified
in the release notes/documentation. It is also assumed that due to
backward compatibility users can safely use this extension
+1 to make extensions as independent as possible.
Doubt if we can do it for each module.
We have, ignite-hibernate_4.2, ignite-hibernate_5.1 modules that attached to
specific hibernate version by their name.
> 11 нояб. 2020 г., в 11:19, Alexey Goncharuk
> написал(а):
>
> Hello Mikhail,
>
>
Hello Mikhail,
I see that now only Ignite dependencies are marked as 'provided', however,
it makes sense to move all libraries being integrated to the 'provided'
scope (for example, the Apache Camel dependency for camel-ext and so on).
This is how it is currently done for the
Igniters,
It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?
The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].
Could some committer take a final look?
[1] -
Hi
Alex,
Yes, we can start releasing the extensions modules. I would like to also
help in releasing a few extensions, it will also help me to be familiarized
with the release process.
Mikhail and I have been having discussion about whether we should use
provided scope for dependencies or shall
Alex,
Should we create a dedicated ticket for the documentation changes or can we
reuse IGNITE-13634? As a bare minimum, we need to update maven artifacts'
names and versions:
https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
-
Denis
On Wed, Oct 28, 2020 at
Igniters,
Since Ignite 2.9 has been released, I think we can now release the
extension modules related to streaming.
I noticed that unlike spring autoconfigure, the streamer extensions
dependencies do not have provided scope, so I created a ticket to fix that
[1]. Anything else we should fix
