[IGNITE-11467] Support Automatic modules for ignite-spring: Move of classes to a separate package or jar

• Type: Sub-task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Dmitry Pavlov
• Created: 04/Mar/19 14:08
• Updated: 17/Jul/22 10:00

Description

Provided that IGNITE-11464 is fixed and lucene is excluded from dependencies, we still need refactor following packages to avoid packages conflicts:

error: the unnamed module reads package org.apache.ignite from both ignite.spring and ignite.core
error: the unnamed module reads package org.apache.ignite.internal.util.spring from both ignite.spring and ignite.core
error: the unnamed module reads package org.apache.ignite.internal.processors.resource from both ignite.spring and ignite.core

One from class in conflicting packages is org.apache.ignite.IgniteSpringBean, which may be referenced outside of Ignite.

It mentioned at least here http://qaru.site/questions/14880736/how-to-connect-apache-ignite-node-by-static-ip-address with full class name:
<bean id="ignite-configuration" class="org.apache.ignite.IgniteSpringBean">

Other conflicts

• org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl in spring and interface org.apache.ignite.internal.util.spring.IgniteSpringHelper in core

Conflicting classes from org.apache.ignite.internal.processors.resource

• GridResourceSpringBeanInjector
• GridSpringResourceContextImpl

Issue Links

• is blocked by: IGNITE-11464 Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts