[
https://issues.apache.org/jira/browse/IGNITE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221262#comment-17221262
]
Mikhail Petrov commented on IGNITE-13621:
-----------------------------------------
[~samaitra],
If Ignite version will be specified explicitly, version of Ignite that user can
use in their project will depend on version of spring-extension. To overcome
this extensions release must be done for each core release but, as I see from
the conversation, it should be avoided.
{code:java}
> The goal is to avoid the practice of publishing Flink or any other extension
> to Maven for every core release if there are no > changes.
> "+" sign implying that the updated extensions will work for Ignite 2.9 and
> later until we need to update them again creating a > release branch like
> "ignite-core-2.14+"{code}
It seems that Spring-data modules should not depend on Ignite version at all.
And "provided" scope can help to use this extension with any version of Ignite
that user needs.
WDYT?
> Remove dependency of spring-data modules on Ignite version
> ----------------------------------------------------------
>
> Key: IGNITE-13621
> URL: https://issues.apache.org/jira/browse/IGNITE-13621
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Minor
>
> It's needed to remove dependency of spring-data modules on Ignite version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
