[
https://issues.apache.org/jira/browse/TIKA-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048216#comment-18048216
]
Hudson commented on TIKA-4598:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1138 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1138/])
TIKA-4598: Move tika-pipes-ignite from plugin to standalone module (#2499)
(github:
[https://github.com/apache/tika/commit/d5918e6ebf44a6499c88b40184d20abcaaccb744])
* (edit) tika-grpc/pom.xml
* (delete) tika-pipes/tika-pipes-plugins/tika-pipes-ignite/README.md
* (delete) tika-pipes/tika-pipes-plugins/tika-pipes-ignite/pom.xml
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/test/java/org/apache/tika/pipes/ignite/IgniteConfigStoreTest.java
* (edit) tika-pipes/tika-pipes-plugins/pom.xml
* (add) tika-pipes/tika-pipes-config-store-ignite/README.md
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/test/java/org/apache/tika/pipes/ignite/IgniteConfigStoreTest.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/assembly/assembly.xml
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/ignite/config/IgniteConfigStoreConfig.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/ignite/server/IgniteStoreServer.java
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/main/java/org/apache/tika/pipes/ignite/server/IgniteStoreServer.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/ignite/IgniteConfigStore.java
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/main/java/org/apache/tika/pipes/ignite/IgniteConfigStore.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/resources/plugin.properties
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/ignite/ExtensionConfigDTO.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/ignite/IgniteConfigStoreFactory.java
* (delete)
tika-pipes/tika-pipes-plugins/tika-pipes-ignite/src/main/java/org/apache/tika/pipes/plugin/ignite/IgnitePipesPlugin.java
* (edit) tika-pipes/pom.xml
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/main/java/org/apache/tika/pipes/ignite/IgniteConfigStoreFactory.java
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/main/java/org/apache/tika/pipes/ignite/ExtensionConfigDTO.java
* (add)
tika-pipes/tika-pipes-config-store-ignite/src/main/java/org/apache/tika/pipes/ignite/config/IgniteConfigStoreConfig.java
* (add) tika-pipes/tika-pipes-config-store-ignite/pom.xml
> Remove plugin architecture from tika-pipes-ignite and move to tika-pipes level
> ------------------------------------------------------------------------------
>
> Key: TIKA-4598
> URL: https://issues.apache.org/jira/browse/TIKA-4598
> Project: Tika
> Issue Type: Task
> Reporter: Nicholas DiPiazza
> Assignee: Nicholas DiPiazza
> Priority: Major
>
> h2. Background
> Currently tika-pipes-ignite is structured as a PF4J plugin, but it's no
> longer needed as a plugin since:
> * Ignite dependencies are now included directly in tika-grpc
> * IgniteConfigStore is registered as a built-in ConfigStore type
> * The plugin classloader was causing conflicts with Ignite's peer class
> loading
> Would be nice to maybe one day make it a pf4j plugin! But I struggled for a
> weekend to try to make it happen and was stuck with classes not being loaded
> from the pf4j plugin classloader. It may very well be that ignite doesn't
> work within pf4j which makes sense because it is a pretty complex piece of
> software.
> h2. Proposed Changes
> # Move tika-pipes-ignite from {{tika-pipes/tika-pipes-plugins/}} to
> {{tika-pipes/}} as a regular module
> # Remove all PF4J plugin annotations and dependencies (@Extension, etc.)
> # Update module structure to be a standard Maven module at the tika-pipes
> level
> # Remove plugin.properties and other PF4J metadata
> # Update parent POMs to reflect the new location
> # Ensure IgniteConfigStore remains registered in ConfigStoreFactory as a
> built-in type
> h2. Benefits
> * Simpler module structure
> * No classloader conflicts
> * Clearer dependency management
> * Consistent with other ConfigStore implementations (memory, file)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
