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

Mikhail Petrov updated IGNITE-16850:
------------------------------------
    Description: 
Spring-data-commons module in extensions repository contains classes that 
provide 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.

Currently it is treated as a separate extensions and has a separate release 
lifecycle.  
Actually we don't need that - currently it just creates unnecessary 
dependencies across extensions. 

Let's 
1. Rename Spring-data-commons  module to ignite-facade
2. Stop publishing or installing this module to local repository.
3. Automatically include ignite-facade module classes in dependency extensions 
jars.

  was:
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. 


> [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
>
> Spring-data-commons module in extensions repository contains classes that 
> provide 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.
> Currently it is treated as a separate extensions and has a separate release 
> lifecycle.  
> Actually we don't need that - currently it just creates unnecessary 
> dependencies across extensions. 
> Let's 
> 1. Rename Spring-data-commons  module to ignite-facade
> 2. Stop publishing or installing this module to local repository.
> 3. Automatically include ignite-facade module classes in dependency 
> extensions jars.



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

Reply via email to