You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2021/10/14 17:00:05 UTC

[jira] [Updated] (IGNITE-15751) [Extensions] Refactor dependencies of Ignite Spring integration extensions

     [ https://issues.apache.org/jira/browse/IGNITE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Petrov updated IGNITE-15751:
------------------------------------
    Description: Now all Ignite Spring integration extensions depend on ignite-spring dependency. Its main use is to configure Ignite client node which is used by extensions to connect to Ignite cluster via xml. ignite-spring depends on pinned version of Spring that in many cases conflicts with Spring version in user project. So to simplify usage of ignite extensions for users that don't need Ignite node configuration through xml it is proposed to eliminate ignite-spring dependency where it is possible and make it up to user to add this dependency to classpath or not.  (was: Now all Ignite Spring integration extensions depend on ignite-spring dependency. Its main use is to configure Ignite client node which is used by extensions to connect to Ignite cluster via xml. ignite-spring depends on pinned version of Spring that in many cases conflicts with Spring version in user project. So to simplify usage of ignite extensions for users that don't need Ignite node configuration through xml. it is proposed to mark ignite-spring dependency as optional.)
        Summary: [Extensions]  Refactor dependencies of Ignite Spring integration extensions  (was: [Extensions] Mark ignite-spring dependency as optional )

> [Extensions]  Refactor dependencies of Ignite Spring integration extensions
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-15751
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15751
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Major
>
> Now all Ignite Spring integration extensions depend on ignite-spring dependency. Its main use is to configure Ignite client node which is used by extensions to connect to Ignite cluster via xml. ignite-spring depends on pinned version of Spring that in many cases conflicts with Spring version in user project. So to simplify usage of ignite extensions for users that don't need Ignite node configuration through xml it is proposed to eliminate ignite-spring dependency where it is possible and make it up to user to add this dependency to classpath or not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)