This is an automated email from the ASF dual-hosted git repository. tballison pushed a commit to branch fix-http-artifact-location in repository https://gitbox.apache.org/repos/asf/tika.git
commit 1b0657b95694b1ee4d2890c41ca22d2bf183a36b Author: tallison <[email protected]> AuthorDate: Thu Jun 25 14:33:24 2026 -0400 beta-1 release fix --- .../tika-pipes-plugins/tika-pipes-http/pom.xml | 31 ++++++++++++++++++---- 1 file changed, 26 insertions(+), 5 deletions(-) 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 90336cde36..314e2b5567 100644 --- a/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml +++ b/tika-pipes/tika-pipes-plugins/tika-pipes-http/pom.xml @@ -156,8 +156,33 @@ <goals> <goal>single</goal> </goals> + </execution> + </executions> + </plugin> + <!-- The plugin zip is built into target/ (the release artifact, like every other plugin). + Copy it into target/plugins/ so the self-test can load it via PF4J + (plugin-roots=target/plugins). Bound after make-assembly (process-test-resources). --> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-resources-plugin</artifactId> + <executions> + <execution> + <id>copy-plugin-zip-for-self-test</id> + <phase>process-test-classes</phase> + <goals> + <goal>copy-resources</goal> + </goals> <configuration> <outputDirectory>${project.build.directory}/plugins</outputDirectory> + <resources> + <resource> + <directory>${project.build.directory}</directory> + <includes> + <include>${project.artifactId}-${project.version}.zip</include> + </includes> + <filtering>false</filtering> + </resource> + </resources> </configuration> </execution> </executions> @@ -185,10 +210,6 @@ 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. - - tika-pipes-http writes its zip to target/plugins/ (not target/) so - that its own self-tests can load the plugin via PF4J in deployment - mode; reflect that path here. --> <execution> <id>install-plugin-zip-locally</id> @@ -197,7 +218,7 @@ <goal>install-file</goal> </goals> <configuration> - <file>${project.build.directory}/plugins/${project.artifactId}-${project.version}.zip</file> + <file>${project.build.directory}/${project.artifactId}-${project.version}.zip</file> <groupId>${project.groupId}</groupId> <artifactId>${project.artifactId}</artifactId> <version>${project.version}</version>
