mraible opened a new pull request, #261: URL: https://github.com/apache/roller/pull/261
Roller 7.0 now requires Java 21. Lucene 10 and Derby 10.17 are compiled for it, and Derby 10.17.1.0 fixes CVE-2022-46337. Derby is only used by tests, `jetty:run` and `db-utils`. Java 21: - The compiler release is 21 in the root pom and `it-playwright`. - CI builds on JDK 21 and 25. The dev-build upload, license, UI-test and CodeQL jobs use 21. - The Dockerfile uses `maven:3.9.16-eclipse-temurin-21` and `tomcat:11.0.29-jdk21-temurin`, pinned instead of the old floating tags. - README, CHANGES.md and the install guide say Java 21. The install guide's other prerequisites (Java EE 6, Servlet 2.4, Tomcat 8, Jetty 9, JPA 2.0, the 6.0.0 archive names) are brought up to date too. Lucene 9.12.3 → 10.6.0: - `IndexSearcher.doc()` is gone. Results now read stored fields through `searcher.storedFields()`, fetched on the thread that reads them. - `TotalHits.value` became `value()`. The exact total and the `search.results.max` cap behave as before; `SearchResultLimitTest` still passes. - **Existing indexes.** Lucene 10 opens a Roller 6.1.7 index through backward-codecs. A 6.1.0–6.1.6 index is rebuilt because of its removed fields, as 6.1.7 already did. Roller 6.0's Lucene 8 index throws `IndexFormatTooOldException`. Master already caught that and scheduled a rebuild, but left no index behind, so searches failed until the rebuild finished. Now an empty index is created right away, and the log gets one line instead of a stack trace. - `IndexUpgradeTest` covers this with real fixtures written by Lucene 8.3.0 and 9.12.3 using Roller 6.0's and 6.1.7's fields. CHANGES.md and the install guide say no operator action is needed. Derby 10.16.1.1 → 10.17.1.0 needed no setup changes. The dependencies and the classes Roller uses are in the same jars. `mvn clean install` passes on JDK 21 and JDK 25: 661 tests, 2 new. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
