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

Ivan Zlenko updated IGNITE-26228:
---------------------------------
    Description: 
We have a lot of common utility methods and classes sprinkled here and there 
which sometimes need to be accessed from the most basic modules of our product. 
Like ignite-core or ignite-api. We need to carefully gather them and place into 
additional module like ignite-common. This module should not have any 
dependencies on any other ignite modules. 

Example of such encounters:
* capacity method needed for both ignite-core and ignite-api modules.
* PartitionSet class which we could utilize in many other places.  

  was:
Implementation classes should never be placed inside the API module.

Let's clear the mess we have right now with classes like TupleImpl


> Create a module with common utils
> ---------------------------------
>
>                 Key: IGNITE-26228
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26228
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Zlenko
>            Priority: Major
>              Labels: ignite-3
>
> We have a lot of common utility methods and classes sprinkled here and there 
> which sometimes need to be accessed from the most basic modules of our 
> product. Like ignite-core or ignite-api. We need to carefully gather them and 
> place into additional module like ignite-common. This module should not have 
> any dependencies on any other ignite modules. 
> Example of such encounters:
> * capacity method needed for both ignite-core and ignite-api modules.
> * PartitionSet class which we could utilize in many other places.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to