[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-11461: --- Priority: Minor (was: Critical) > 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: Dmitry Pavlov >Priority: Minor > Time Spent: 1h > 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 || > Notes || > |ignite-code|(/)|(/)| | > |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use > ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is > required by user manually. | > |ignite-compress | (x) | (/) not releaseed | > org.apache.ignite.internal.processors.compress package conflict | > |ignite-direct-io|(x) blocked by indexind | (/) | > org.apache.ignite.internal.processors.cache.persistence.file package conflict > | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected | | > |ignite-ml |(x) blocked by indexing | | | > |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - > EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| | > |ignite-slf4j | (/)|(/)| | > |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | > (/) | Usage with slf4j may break compilation because conflict of packages | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API > breaking is possibleif hibernate core classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | | > |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging > from both commons.logging and spring.jcl conflict | > https://jira.spring.io/browse/SPR-16605 | > |ignite-ml | (/) master (x) 2.7 | | | > |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | > Only spring needs to be fixed | -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-11461: --- Fix Version/s: (was: 2.9) > 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: Dmitry Pavlov >Priority: Critical > Time Spent: 1h > 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 || > Notes || > |ignite-code|(/)|(/)| | > |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use > ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is > required by user manually. | > |ignite-compress | (x) | (/) not releaseed | > org.apache.ignite.internal.processors.compress package conflict | > |ignite-direct-io|(x) blocked by indexind | (/) | > org.apache.ignite.internal.processors.cache.persistence.file package conflict > | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected | | > |ignite-ml |(x) blocked by indexing | | | > |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - > EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| | > |ignite-slf4j | (/)|(/)| | > |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | > (/) | Usage with slf4j may break compilation because conflict of packages | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API > breaking is possibleif hibernate core classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | | > |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging > from both commons.logging and spring.jcl conflict | > https://jira.spring.io/browse/SPR-16605 | > |ignite-ml | (/) master (x) 2.7 | | | > |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | > Only spring needs to be fixed | -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11461: - Fix Version/s: (was: 2.8) 2.9 > 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: Dmitry Pavlov >Priority: Critical > Fix For: 2.9 > > Time Spent: 1h > 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 || > Notes || > |ignite-code|(/)|(/)| | > |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use > ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is > required by user manually. | > |ignite-compress | (x) | (/) not releaseed | > org.apache.ignite.internal.processors.compress package conflict | > |ignite-direct-io|(x) blocked by indexind | (/) | > org.apache.ignite.internal.processors.cache.persistence.file package conflict > | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected | | > |ignite-ml |(x) blocked by indexing | | | > |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - > EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| | > |ignite-slf4j | (/)|(/)| | > |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | > (/) | Usage with slf4j may break compilation because conflict of packages | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API > breaking is possibleif hibernate core classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | | > |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging > from both commons.logging and spring.jcl conflict | > https://jira.spring.io/browse/SPR-16605 | > |ignite-ml | (/) master (x) 2.7 | | | > |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | > Only spring needs to be fixed | -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11461: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > 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: Dmitry Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 1h > 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 || > Notes || > |ignite-code|(/)|(/)| | > |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use > ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is > required by user manually. | > |ignite-compress | (x) | (/) not releaseed | > org.apache.ignite.internal.processors.compress package conflict | > |ignite-direct-io|(x) blocked by indexind | (/) | > org.apache.ignite.internal.processors.cache.persistence.file package conflict > | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected | | > |ignite-ml |(x) blocked by indexing | | | > |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - > EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| | > |ignite-slf4j | (/)|(/)| | > |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | > (/) | Usage with slf4j may break compilation because conflict of packages | > |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API > breaking is possibleif hibernate core classes not used by third party code | > |ignite-zookeeper| (x) IGNITE-11486 | (/) | | > |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging > from both commons.logging and spring.jcl conflict | > https://jira.spring.io/browse/SPR-16605 | > |ignite-ml | (/) master (x) 2.7 | | | > |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | > Only spring needs to be fixed | -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | (/) | Only spring needs to be fixed | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | Only spring needs to be fixed | > 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:
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | |ignite-cassandra-store | (x) [IGNITE-11467] blocked by spring | Only spring needs to be fixed | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | > 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 >
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | > 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
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexind | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexing, blocked by compress | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | > 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: >
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexing, blocked by compress | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected | | |ignite-ml |(x) blocked by indexing | | | |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | |ignite-slf4j | (/)|(/)| | |ignite-rest-http | (x) IGNITE-11469 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexing, blocked by compress | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | > 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
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |ignite-compress | (x) | (/) not releaseed | org.apache.ignite.internal.processors.compress package conflict | |ignite-direct-io|(x) blocked by indexing, blocked by compress | (/) | org.apache.ignite.internal.processors.cache.persistence.file package conflict | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | > 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
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | |ignite-ml | (/) master (x) 2.7 | | | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | > 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 >
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict | https://jira.spring.io/browse/SPR-16605 | 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict https://jira.spring.io/browse/SPR-16605 | > 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 >
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |ignite-code|(/)|(/)| | |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is required by user manually. | |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API breaking is possibleif hibernate core classes not used by third party code | |ignite-zookeeper| (x) IGNITE-11486 | (/) | | |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging from both commons.logging and spring.jcl conflict https://jira.spring.io/browse/SPR-16605 | 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 || Notes || |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |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 || > Notes || > |ignite-code|(/)|(/)| | >
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 || Notes || |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 | (/) | Usage with slf4j may break compilation because conflict of packages | |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|(/)|(/) 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 | (/) | > 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 || > Notes || > |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
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 |
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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|(/)|(/) - 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 | > 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|(/)|(/) - 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
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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|(/)|(/) - 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 | 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 | (/) | > 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|(/)|(/) - 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 | > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| |ignite-rest-http | (x) IGNITE-11469 | (/) | 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 | (/)|(/)| > 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|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > |ignite-slf4j | (/)|(/)| > |ignite-rest-http | (x) IGNITE-11469 | (/) | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |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 | (/)|(/)| > 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|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > |ignite-slf4j | (/)|(/)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |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 | (/)|(/)| 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |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 | | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |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 | (/)|(/)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affercted| |ignite-ml |(x) blocked by indexing | | 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | |ignite-ml |(x) blocked by indexing | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affercted| > |ignite-ml |(x) blocked by indexing | | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |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 | | 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affercted| |ignite-ml |(x) blocked by indexing | | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |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 | | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | |ignite-ml |(x) blocked by indexing | 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) blocked by indexing | > |ignite-ml |(x) blocked by indexing | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) blocked by indexing | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 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 Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) | 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) | > 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 > 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 > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) | 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | > 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 > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x)| > 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 > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) blocked by indexing | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ 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 ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x)| was: Example of failure in 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 > 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 > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Fix Version/s: 2.8 > 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 > > > Example of failure in 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 message was sent by Atlassian JIRA (v7.6.3#76005)
