[
https://issues.apache.org/jira/browse/IGNITE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-24781.
--------------------------------------
Resolution: Fixed
> IEP-119 Move common classes to ignite-commons
> ---------------------------------------------
>
> Key: IGNITE-24781
> URL: https://issues.apache.org/jira/browse/IGNITE-24781
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: IEP-119, ise
>
> Umbrella ticket for and Phase 1 of IEP-119 - Refactoring.
> We want to move all common for ignite-core and future ignite-binary modules
> to ignite-commons module:
> Specifically, we want to move to ignite-commons the following packages:
> # org.apache.ignite.lang.*
> # org.apache.ignite.internal.util.*
> Except the classes used only in core core - each class need to be
> investigated separately.
> While this work in progress ignite-commons must compile classes directly to
> ignite-core/target/classes folder to preserve binary content.
> Refactoring comes from the fact that `org.apache.ignite.binary` package
> classes heavily relies on the above packages and classes like
> `org.apache.ignite.internal.util.typedef.internal.A`,
> `org.apache.ignite.internal.util.typedef.internal.F`, `IgniteException`, etc.
> therefore prior to moving even public API to separate module we must move
> dependecy classes to something more clear then ignite-core.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
