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

Hudson commented on TIKA-4587:
------------------------------

SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1126 (See 
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1126/])
TIKA-4587: Add pf4j development mode support to TikaPluginManager (#2473) 
(github: 
[https://github.com/apache/tika/commit/89b2bf9cfe70969ed5d67d03da5006633233ce5f])
* (edit) 
tika-plugins-core/src/main/java/org/apache/tika/plugins/TikaPluginManager.java
* (add) 
tika-plugins-core/src/test/java/org/apache/tika/plugins/TikaPluginManagerTest.java
* (edit) tika-grpc/README.md


> Add pf4j development mode support to TikaPluginManager
> ------------------------------------------------------
>
>                 Key: TIKA-4587
>                 URL: https://issues.apache.org/jira/browse/TIKA-4587
>             Project: Tika
>          Issue Type: Improvement
>          Components: tika-pipes
>            Reporter: Nicholas DiPiazza
>            Priority: Minor
>
> h2. Problem
> Currently, TikaPluginManager requires plugins to be packaged as ZIP files in 
> the configured plugin-roots directories. This adds friction to plugin 
> development since developers must rebuild and repackage plugins as ZIPs to 
> test changes.
> h2. Solution
> Add support for pf4j's development mode which allows loading plugins directly 
> from unpackaged directories (e.g., target/classes). This would enable faster 
> development iteration by eliminating the ZIP packaging step during 
> development.
> h2. Implementation Approach
> * Add a way to configure RuntimeMode (DEVELOPMENT vs DEPLOYMENT) in 
> TikaPluginManager
> * When in DEVELOPMENT mode, allow plugin-roots to point to unpackaged plugin 
> directories
> * Configure via environment variable (TIKA_PLUGIN_DEV_MODE) or system 
> property (tika.plugin.dev.mode)
> * Skip ZIP extraction when in development mode
> * Default to DEPLOYMENT mode for backward compatibility
> h2. Benefits
> * Faster plugin development cycle - no need to rebuild ZIP files during 
> development
> * Easier debugging of plugin code
> * Consistent with pf4j best practices
> h2. References
> * pf4j development mode docs: https://pf4j.org/doc/development-mode.html
> * Pull request: https://github.com/apache/tika/pull/new/pf4j-development-mode



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to