[IGNITE-11464] Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts

• Type: Sub-task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Dmitry Pavlov
• Created: 01/Mar/19 13:57
• Updated: 17/Jul/22 10:00

Description

error: the unnamed module reads package org.apache.lucene.search from both lucene.sandbox and lucene.core
error: the unnamed module reads package org.apache.lucene.document from both lucene.sandbox and lucene.core
error: the unnamed module reads package org.apache.lucene.analysis.standard from both lucene.core and lucene.analyzers.common
error: the unnamed module reads package org.apache.ignite.internal.processors.cache.query from both ignite.indexing and ignite.core
error: the unnamed module reads package org.apache.ignite.internal.visor.verify from both ignite.indexing and ignite.core 
....
C:\projects\incubator-ignite\modules\dev-utils\ignite-modules-test\src\test\java\module-info.java:18: error: module ignite_modules_test reads package org.apache.lucene.search from both lucene.sandbox and lucene.core
module ignite_modules_test 

 

Some of these errors probably can be fixed by workarounds for dependencies:

2 errors coming from duplicate packages declared in code and indexing:

• error: module ignite.core reads package org.apache.ignite.internal.processors.cache.query from both ignite.indexing and ignite.core
• error: module ignite.core reads package org.apache.ignite.internal.visor.verify from both ignite.indexing and ignite.core

Issue Links

• blocks: IGNITE-11467 Support Automatic modules for ignite-spring: Move of classes to a separate package or jar
• links to: GitHub Pull Request #6224