[
https://issues.apache.org/jira/browse/IGNITE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223096#comment-17223096
]
Alexey Goncharuk commented on IGNITE-13621:
-------------------------------------------
[~samaitra],
I if we fix the Ignite version in an extension pom, we will prevent it from
being used with later versions of Ignite. Say, ignite-spring-data-ext-1.0.0 was
released with ignite-2.9 in its dependencies. If a user decides to go with
ignite-2.10 and the same version of the extension (assuming nothing has changed
in the extension and it is still compatible), the user will have to add maven
excludes to their project in order to avoid conflicts. In my opinion, this is
not very user-friendly, and I saw that [~nizhikov] used provided scope for
spring-boot-autoconfigure extensions.
However, indeed, we may need a separate [DISCUSS] thread to have a formal
agreement.
> 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)
