This is an automated email from the ASF dual-hosted git repository.

tballison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tika.git


The following commit(s) were added to refs/heads/main by this push:
     new 3bbf65cbe1 TIKA-4723 follow-up: fix sqlite3 shade filter and correct 
docs (#2810)
3bbf65cbe1 is described below

commit 3bbf65cbe19c49de1a6868c9ca39cc45744265b0
Author: Nicholas DiPiazza <[email protected]>
AuthorDate: Wed May 13 01:11:18 2026 +0000

    TIKA-4723 follow-up: fix sqlite3 shade filter and correct docs (#2810)
    
    * TIKA-4723 follow-up: align sqlite3 shade filter with scientific/nlp 
packages
    
    Add module-info.class, META-INF/LICENSE.md, and META-INF/NOTICE.md
    exclusions to the maven-shade-plugin filter in tika-parser-sqlite3-package.
    These were present in tika-parser-scientific-package and
    tika-parser-nlp-package but missing in sqlite3, which could cause
    duplicate module-info.class entries in the shaded jar on Java 9+.
    
    Co-authored-by: Copilot <[email protected]>
    
    * TIKA-4723 follow-up: fix incorrect TikaConfigException claim in 
release-artifacts.adoc
    
    The doc stated that starting tika-grpc with no plugins loaded triggers a
    TikaConfigException. The actual behaviour (TikaGrpcServerImpl.java line 133)
    is a LOG.warn with a helpful download URL; the server continues to start.
    Correct the doc to match the real code path.
    
    Co-authored-by: Copilot <[email protected]>
    
    * Potential fix for pull request finding
    
    Co-authored-by: Copilot Autofix powered by AI 
<[email protected]>
    
    ---------
    
    Co-authored-by: Copilot <[email protected]>
    Co-authored-by: Copilot Autofix powered by AI 
<[email protected]>
---
 .../ROOT/pages/maintainers/release-guides/release-artifacts.adoc   | 7 ++++---
 .../tika-parsers-extended/tika-parser-sqlite3-package/pom.xml      | 3 +++
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git 
a/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc 
b/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc
index 49c2f187b9..587edf0104 100644
--- a/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc
+++ b/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc
@@ -170,9 +170,10 @@ plugins) locally; that build output is the build context 
for the
 `apache/tika-grpc` image and isn't published as a release artifact in its
 own right.
 
-tika-grpc requires at least one pf4j plugin to be loaded at startup; an
-empty `plugins/` directory triggers a `TikaConfigException` with a
-download URL pointing at Apache dist.
+tika-grpc expects pf4j plugins for full functionality; starting without
+plugins logs a warning with a download URL pointing at Apache dist.
+Most fetcher-dependent RPC calls will fail at runtime if no plugins are
+present.
 
 === Server: slim jar on Central, bin.zip on dist
 
diff --git 
a/tika-parsers/tika-parsers-extended/tika-parser-sqlite3-package/pom.xml 
b/tika-parsers/tika-parsers-extended/tika-parser-sqlite3-package/pom.xml
index ec7d8dc82e..f21a1b3a58 100644
--- a/tika-parsers/tika-parsers-extended/tika-parser-sqlite3-package/pom.xml
+++ b/tika-parsers/tika-parsers-extended/tika-parser-sqlite3-package/pom.xml
@@ -83,11 +83,14 @@
                 <filter>
                   <artifact>*:*</artifact>
                   <excludes>
+                    <exclude>module-info.class</exclude>
                     <exclude>META-INF/*.SF</exclude>
                     <exclude>META-INF/*.DSA</exclude>
                     <exclude>META-INF/*.RSA</exclude>
                     <exclude>META-INF/DEPENDENCIES</exclude>
                     <exclude>META-INF/MANIFEST.MF</exclude>
+                    <exclude>META-INF/LICENSE.md</exclude>
+                    <exclude>META-INF/NOTICE.md</exclude>
                   </excludes>
                 </filter>
               </filters>

Reply via email to