ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11467) Support Automatic modules for ignite-spring: Move of classes to a separate package or jar
Date Mon, 04 Mar 2019 14:09:00 GMT
Dmitriy Pavlov created IGNITE-11467:
---------------------------------------

             Summary: 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: Dmitriy Pavlov


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">



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message