[jira] [Commented] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts

["Dmitry Pavlov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567595#comment-17567595 ] 

Dmitry Pavlov commented on IGNITE-11461:
----------------------------------------

[~soc] thanks for noticing. I've changed the priority to minor.

At 2019 some project started to migrate to jigsaw, and we were expecting mass migration. Actually, it didn't happened, so minor or trivial is more appropriate here.

During this research I've also found that external dependencies weren't modular-ready, as well. So here we were blocked by our deps. I don't know if it is true right now.

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