Thank you, Tilman! 17063cab may fix that issue. What I can't figure out is what spotless thought needed to be fixed.
On Thu, Mar 19, 2026 at 12:37 AM Tilman Hausherr <[email protected]> wrote: > > +1 > > Successful build on oracle jdk11, however I had to disable checkstyle. > For some reason a java file in the tika-handler-boilerpipe subproject > had windows style line ends, which isn't in the original file. > > tika3\tika-handlers\tika-handler-boilerpipe\src\main\java\org\apache\tika\sax\boilerpipe\BoilerpipeContentHandler.java > > When fixing it with the editor, it came back in the next build, could it > be that spotless is doing this when building when fixing the import? > > [INFO] --- spotless:2.46.1:apply (default) @ tika-handler-boilerpipe --- > [INFO] Index file does not exist. Fallback to an empty index > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.googlejavaformat.java.RemoveUnusedImports > (file:/XXXXXX/repository/com/google/googlejavaformat/google-java-format/1.24.0/google-java-format-1.24.0.jar) > to method com.sun.tools.javac.tree.JCTree$JCImport.getQualifiedIdentifier() > WARNING: Please consider reporting this to the maintainers of > com.google.googlejavaformat.java.RemoveUnusedImports > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] clean file: > V:\tika-3.3.0-src\tika-3.3.0\tika-handlers\tika-handler-boilerpipe\src\main\java\org\apache\tika\sax\boilerpipe\BoilerpipeContentHandler.java > [INFO] Spotless.Java is keeping 1 files clean - 1 were changed to be > clean, 0 were already clean, 0 were skipped because caching determined > they were already clean > > > Also the name is missing its pom.xml so the output looks like this: > > [INFO] Apache Tika PDF parser module ...................... SUCCESS [ 24.181 > s] > [INFO] Apache Tika package parser module .................. SUCCESS [ 5.101 > s] > [INFO] Apache Tika WARC parser module ..................... SUCCESS [ 3.474 > s] > [INFO] Apache Tika handlers ............................... SUCCESS [ 0.126 > s] > [INFO] tika-handler-boilerpipe ............................ FAILURE [ 0.253 > s] > [INFO] Apache Tika standard parser package ................ SKIPPED > [INFO] Apache Tika Detectors .............................. SKIPPED > [INFO] Apache Tika Siegfried wrapper ...................... SKIPPED > [INFO] Apache Tika magika wrapper ......................... SKIPPED > > > > Tilman > > Am 18.03.2026 um 22:07 schrieb Tim Allison: > > A candidate for the Tika 3.3.0 release is available at: > > https://dist.apache.org/repos/dist/dev/tika/3.3.0 > > > > The release candidate is a zip archive of the sources in: > > https://github.com/apache/tika/tree/3.3.0-rc1/ > > > > The SHA-512 checksum of the archive is > > 03b93dfaf8c167e9e0f5d9c9424245296e821faffe60eb1967b6e82839fcb14806047094c66caf4c10a494db34b1cb2b2f22827c3c4b3c3eab8732914b12efbb. > > > > In addition, a staged maven repository is available here: > > https://repository.apache.org/content/repositories/orgapachetika-1122/org/apache/tika > > > > Please vote on releasing this package as Apache Tika 3.3.0. > > The vote is open for the next 72 hours and passes if a majority of at > > least three +1 Tika PMC votes are cast. > > > > [ ] +1 Release this package as Apache Tika 3.3.0 > > [ ] -1 Do not release this package because... > > > > Here's my +1. > > > > Thank you! > > > > Best, > > > > Tim >
