[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov updated IGNITE-11461: ------------------------------------ Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io This type of failure is named package inference, but it is strictly prohibited http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Following table contains currenly investigated Ignite modules if this applicability as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is required from our pom.xml or by user | |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) But logging itself may be not operational - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| |ignite-rest-http | (x) IGNITE-11469 | (/) | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) if hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io This type of failure is named package inference, but it is strictly prohibited http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Following table contains currenly investigated Ignite modules if this applicability as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is required from our pom.xml or by user | |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| |ignite-rest-http | (x) IGNITE-11469 | (/) | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) if hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > -------------------------------------------------------------------------------- > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement > Reporter: Dmitriy Pavlov > Assignee: Dmitriy Pavlov > Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > This type of failure is named package inference, but it is strictly > prohibited > http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Following table contains currenly investigated Ignite modules if this > applicability as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is > required from our pom.xml or by user | > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | > |ignite-log4j|(/)|(/) But logging itself may be not operational - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > |ignite-slf4j | (/)|(/)| > |ignite-rest-http | (x) IGNITE-11469 | (/) | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) if hibernate core > classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | -- This message was sent by Atlassian JIRA (v7.6.3#76005)