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 2022/04/22 11:23:00 UTC

[jira] [Updated] (IGNITE-16850) [Extensions] Exclude spring-data-commons module from publishing.

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

Mikhail Petrov updated IGNITE-16850:
------------------------------------
    Summary: [Extensions] Exclude spring-data-commons module from publishing.  (was: Move IgniteProxy classes from extension module to ignite-core)

> [Extensions] Exclude spring-data-commons module from publishing.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-16850
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16850
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mikhail Petrov
>            Priority: Major
>
> We need to introduce single facade to universal access Ignite functionality via Ignite node and Ignite thin client. It helps to avoid code duplication in cases when both Ignite thin client and Ignite node is used to perform Ignite operations.
> It's already been introduced and widely used in Ignite extensions. So let's move Ignite proxy classes to the Ignite core. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)