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

Dmitry Pavlov updated IGNITE-11467:
-----------------------------------
    Priority: Minor  (was: Major)

> Support Automatic modules for ignite-spring: Move of classes to a separate 
> package or jar
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11467
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11467
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Dmitry Pavlov
>            Priority: Minor
>
> Provided that [IGNITE-11464] is fixed and lucene is excluded from 
> dependencies, we still need refactor following packages to avoid packages 
> conflicts:
> {noformat}
> 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
> {noformat}
> 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



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

Reply via email to