[
https://issues.apache.org/jira/browse/TIKA-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047655#comment-18047655
]
ASF GitHub Bot commented on TIKA-4587:
--------------------------------------
nddipiazza commented on PR #2481:
URL: https://github.com/apache/tika/pull/2481#issuecomment-3692886644
The CI failure in `tika-translate` is unrelated to this PR and has been
filed as [TIKA-4588](https://issues.apache.org/jira/browse/TIKA-4588).
**Root cause:** The `jakarta.websocket:jakarta.websocket-api:jar:2.3.0-M1`
dependency pulls in a SNAPSHOT parent POM
(`org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT`) that is no longer available in
Maven Central.
**This PR only changes:**
- `tika-grpc/pom.xml` (dev profile for plugin development)
- `tika-grpc/run-dev.sh` (convenience script)
- `tika-grpc/README.md` (documentation)
- `tika-grpc/dev-tika-config.json` (config file)
- `tika-plugins-core/.../TikaPluginManager.java` (fix for test failure)
All tests pass locally and the failure is in a completely different module
(`tika-translate`).
> 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)
