This is an automated email from the ASF dual-hosted git repository. tballison pushed a commit to branch TIKA-4833-plugin-zip-package-phase in repository https://gitbox.apache.org/repos/asf/tika.git
commit eb03b307966f08ec784720e7e682ccac7b639a9e Author: tallison <[email protected]> AuthorDate: Tue Aug 25 06:40:36 2026 -0400 update plugin stages to avoid flaky hudson issues --- .../pages/maintainers/release-guides/release-artifacts.adoc | 12 +++++++++++- tika-parent/pom.xml | 3 --- .../tika-pipes-plugins/tika-pipes-atlassian-jwt/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-az-blob/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-csv/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-es/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-file-system/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-gcs/pom.xml | 12 ++++++------ .../tika-pipes-plugins/tika-pipes-google-drive/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-jdbc/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-json/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-kafka/pom.xml | 12 ++++++------ .../tika-pipes-plugins/tika-pipes-microsoft-graph/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-opensearch/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-s3/pom.xml | 12 ++++++------ tika-pipes/tika-pipes-plugins/tika-pipes-solr/pom.xml | 12 ++++++------ 17 files changed, 101 insertions(+), 94 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 00ca098b58..44c7d494b4 100644 --- a/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc +++ b/docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc @@ -146,7 +146,7 @@ API or embedding it programmatically. Mechanism: `maven-assembly-plugin` with `<attach>false</attach>` in each plugin pom (TIKA-4723). Because `<attach>false</attach>` also skips the local-repo install, each plugin pom additionally runs -`maven-install-plugin:install-file` during the `install` phase, writing +`maven-install-plugin:install-file` during the `package` phase, writing the zip into the local repo at canonical coordinates (`<groupId>:<artifactId>:zip:<version>`). Sibling modules (`tika-pipes-fork-parser`, `tika-server-*`, `tika-grpc`, integration @@ -154,6 +154,16 @@ tests) declare the zip as a test-scope Maven dep and rely on this mechanism to resolve it from the local repo without ever publishing it to Central. +The `package` binding is deliberate and must not be moved to `install`. +A reactor `mvn package` — what the `tika-main-jdk21` and `tika-main-jdk26` +Jenkins jobs run, and what a contributor building the tree runs — never +reaches the `install` phase, so an `install`-bound `install-file` leaves +the zip unresolvable and every consuming module fails dependency +resolution. It builds only where a previous `mvn install`/`deploy` on the +same machine happened to leave a matching zip in the local repo, which +made the breakage look intermittent until the `4.0.0` → `4.1.0-SNAPSHOT` +bump invalidated every cached copy. + === tika-grpc tika-grpc is a standalone gRPC server, parallel to tika-server — not built diff --git a/tika-parent/pom.xml b/tika-parent/pom.xml index c19d259e3c..0b438ce97b 100644 --- a/tika-parent/pom.xml +++ b/tika-parent/pom.xml @@ -1504,9 +1504,6 @@ <version>3.3.1</version> <configuration> <autoVersionSubmodules>true</autoVersionSubmodules> - <!-- 'install' (not the default 'verify') so the install-only pf4j plugin zips - (attach=false, installed via install:install-file; see tika-pipes plugins) - are available in the local repo for sibling modules that depend on them. --> <preparationGoals>clean install</preparationGoals> </configuration> <dependencies> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-atlassian-jwt/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-atlassian-jwt/pom.xml index d7544904cd..86b356151e 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-atlassian-jwt/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-atlassian-jwt/pom.xml @@ -131,15 +131,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-az-blob/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-az-blob/pom.xml index 0e9c49d145..52d1dd10a5 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-az-blob/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-az-blob/pom.xml @@ -117,15 +117,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-csv/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-csv/pom.xml index 887da4d961..39e8adddfb 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-csv/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-csv/pom.xml @@ -109,15 +109,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-es/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-es/pom.xml index e8739bec0d..e7fe025c09 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-es/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-es/pom.xml @@ -128,15 +128,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-file-system/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-file-system/pom.xml index 143268ed96..fde5070d52 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-file-system/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-file-system/pom.xml @@ -121,15 +121,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-gcs/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-gcs/pom.xml index b917e01796..2b8ba80eb5 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-gcs/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-gcs/pom.xml @@ -113,15 +113,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-google-drive/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-google-drive/pom.xml index ac0a5f1517..db6b5e804b 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-google-drive/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-google-drive/pom.xml @@ -181,15 +181,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml index 7f69f48875..d716a37f9d 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml @@ -197,15 +197,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-jdbc/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-jdbc/pom.xml index b2d425b0fa..d7533f818d 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-jdbc/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-jdbc/pom.xml @@ -113,15 +113,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-json/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-json/pom.xml index 778de9b15b..418abad8be 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-json/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-json/pom.xml @@ -111,15 +111,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-kafka/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-kafka/pom.xml index 108cf10b03..37dd8dcb42 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-kafka/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-kafka/pom.xml @@ -120,15 +120,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-microsoft-graph/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-microsoft-graph/pom.xml index bd87d879c9..58c3b215ba 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-microsoft-graph/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-microsoft-graph/pom.xml @@ -210,15 +210,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-opensearch/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-opensearch/pom.xml index 55921fbd8b..61b2b8bb1e 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-opensearch/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-opensearch/pom.xml @@ -124,15 +124,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-s3/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-s3/pom.xml index f51eeeb21a..e8ffb28c75 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-s3/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-s3/pom.xml @@ -124,15 +124,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals> diff --git a/tika-pipes/tika-pipes-plugins/tika-pipes-solr/pom.xml b/tika-pipes/tika-pipes-plugins/tika-pipes-solr/pom.xml index ea7059a9db..62ba948860 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-solr/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-solr/pom.xml @@ -143,15 +143,15 @@ <artifactId>maven-install-plugin</artifactId> <executions> <!-- - The assembly attaches the zip with <attach>false</attach> (TIKA-4723) - so it is not added to the Maven artifact set and therefore is not - deployed to Maven Central. Sibling modules declare this plugin zip - as a test-scope Maven dep, so we install-file it locally to satisfy - reactor resolution without making it part of the project artifacts. + The assembly builds the zip with <attach>false</attach> (TIKA-4723) so it + stays out of the Maven artifact set and off Maven Central. Sibling modules + declare it as a test-scope zip dep, so install-file puts it in the local + repo instead. Bound to package, not install: CI and contributors run + `mvn package`, which has to resolve it too. --> <execution> <id>install-plugin-zip-locally</id> - <phase>install</phase> + <phase>package</phase> <goals> <goal>install-file</goal> </goals>
