update plugin stages to avoid flaky hudson issues

Author: tballison

docs/modules/ROOT/pages/maintainers/release-guides/release-artifacts.adoc

@@ -146,14 +146,24 @@ 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
 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

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>

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>

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>

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>

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>

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>

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>

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>

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>