For fun, I restarted the build and got a different error: ... Downloaded from central: https://repo.maven.apache.org/maven2/org/bouncycastle/bcpkix-jdk15on/1.65/bcpkix-jdk15on-1.65.jar (879 kB at 1.7 MB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/bouncycastle/bcprov-jdk15on/1.65/bcprov-jdk15on-1.65.jar (4.5 MB at 7.3 MB/s) [INFO] DOCKER> Pulling from library/elasticsearch 02184a91e435: Pull complete 2602e1c5e883: Pull complete a998be0af0b8: Pull complete ed15297e21ea: Pull complete 8a980f875cea: Pull complete 4f4fb700ef54: Pull complete 5424ef9d14b5: Pull complete d00ed398ddf3: Pull complete a13f6685425f: Pull complete 711be2f9f33b: Pull complete 3fc17721b5ae: Download complete ab63c215921f: Download complete [INFO] DOCKER> Digest: sha256:c0e8efbd41e3bdc912293889bae4402f3166f8d5a642f7f4d711b58dd8c2877e [INFO] DOCKER> Status: Downloaded newer image for elasticsearch:9.2.0 [INFO] DOCKER> Pulled elasticsearch:9.2.0 in 25 seconds [INFO] DOCKER> Pulling from library/logstash 4f4fb700ef54: Pull complete 205b1025b115: Pull complete 4c00b3f750a1: Pull complete bb09c2129a5c: Pull complete c0bda2a661ef: Pull complete 16a8d65ee75e: Pull complete ac97e6df1725: Pull complete 704cc6e755b6: Pull complete a8a9eade8d7e: Download complete 8e79ffcf06ed: Download complete [INFO] DOCKER> Digest: sha256:e73333d13757fb744d45861011fec26410e1131ef4154d86e2b06092d2f0232c [INFO] DOCKER> Status: Downloaded newer image for logstash:9.2.0 [INFO] DOCKER> Pulled logstash:9.2.0 in 21 seconds [INFO] DOCKER> [elasticsearch:9.2.0] "elasticsearch": Start container 04415ba58e2d [ERROR] DOCKER> Error occurred during container startup, shutting down... [INFO] DOCKER> [elasticsearch:9.2.0] "elasticsearch": Stop and removed container 04415ba58e2d after 0 ms [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Apache Log4j BOM 2.26.0: [INFO] [INFO] Apache Log4j BOM ................................... SUCCESS [ 5.259 s] [INFO] Apache Log4j Parent ................................ SUCCESS [ 0.382 s] [INFO] Apache Log4j API Java 9 support .................... SUCCESS [ 2.464 s] [INFO] Apache Log4j API ................................... SUCCESS [ 6.492 s] [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [ 1.545 s] [INFO] Apache Log4j Core .................................. SUCCESS [ 15.950 s] [INFO] Apache Log4j API Tests ............................. SUCCESS [ 9.856 s] [INFO] Apache Log4j Core Tests ............................ SUCCESS [01:24 min] [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [ 10.891 s] [INFO] Apache Log4j App Server Support .................... SUCCESS [ 1.291 s] [INFO] Log4j API to SLF4J Adapter ......................... SUCCESS [ 2.769 s] [INFO] SLF4J 1 Binding for Log4j API ...................... SUCCESS [ 3.259 s] [INFO] Apache Log4j Cassandra ............................. SUCCESS [ 2.577 s] [INFO] Apache Log4j fuzz tests ............................ SUCCESS [ 1.528 s] [INFO] Apache Log4j Core fuzz tests ....................... SUCCESS [ 1.174 s] [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [ 0.762 s] [INFO] Apache Log4j CouchDB ............................... SUCCESS [ 1.559 s] [INFO] Apache Log4j Docker Library ........................ SUCCESS [ 1.505 s] [INFO] Apache Log4j Streaming Interface ................... SUCCESS [ 4.140 s] [INFO] Apache Log4j Jakarta JMS ........................... SUCCESS [ 2.680 s] [INFO] Apache Log4j Jakarta SMTP .......................... SUCCESS [ 2.524 s] [INFO] Apache Log4j Jakarta Web ........................... SUCCESS [ 3.261 s] [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [ 2.264 s] [INFO] Apache Log4j JPA ................................... SUCCESS [ 3.934 s] [INFO] Apache Log4j JDK Platform Logging Adapter .......... SUCCESS [ 2.224 s] [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [ 2.544 s] [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [ 5.674 s] [INFO] Apache Log4j JSON Template Layout .................. SUCCESS [ 3.377 s] [INFO] Apache Log4j JSON Template Layout fuzz tests ....... SUCCESS [ 1.260 s] [INFO] Apache Log4j JSON Template Layout tests ............ FAILURE [ 58.502 s] [INFO] Apache Log4j MongoDB 4 ............................. SKIPPED [INFO] Apache Log4j MongoDB Appender ...................... SKIPPED [INFO] Apache Log4j to JUL Bridge ......................... SKIPPED [INFO] Apache Log4j OSGi tests ............................ SKIPPED [INFO] Apache Log4J Performance Tests ..................... SKIPPED [INFO] SLF4J 2 Provider for Log4j API ..................... SKIPPED [INFO] SLF4J 2 Provider for Log4j API fuzz tests .......... SKIPPED [INFO] Apache Log4j Spring Boot Support ................... SKIPPED [INFO] Apache Log4j Spring Cloud Config Client Support .... SKIPPED [INFO] Apache Log4j Web ................................... SKIPPED [INFO] Apache Log4j Tag Library ........................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 04:06 min [INFO] Finished at: 2026-05-04T14:59:47-04:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (start) on project log4j-layout-template-json-test: Execution start of goal io.fabric8:docker-maven-plugin:0.46.0:start failed: Cannot invoke "com.google.gson.JsonElement.isJsonNull()" because the return value of "com.google.gson.JsonObject.get(String)" is null -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :log4j-layout-template-json-test
Gary On Mon, May 4, 2026 at 2:55 PM Gary Gregory <[email protected]> wrote: > > Since build reproducibility is broken and not a requirement, it should > be marked as optional in the review kit. I am going to ignore it and > use a more simple "mvn clean verify -P docker" check. This gives me: > > [ERROR] Errors: > [ERROR] RollingAppenderDirectCronTest.testAppender:57 » Runtime > java.lang.RuntimeException: Rollover completion verification failure > for file: > /Users/garygregory/rc/log4j-2.26.0/src/log4j-core-test/target/logs/core/appender/rolling/RollingAppenderDirectCronTest_69f8eb82_16734836558386803739/test-2026-05-04T02-54-59.log > [INFO] > [ERROR] Tests run: 8656, Failures: 0, Errors: 1, Skipped: 35 > > Using: > > Openjdk version "17.0.19" 2026-04-21 > OpenJDK Runtime Environment Homebrew (build 17.0.19+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.19+0, mixed mode, sharing) > > Apache Maven 3.9.15 (98b2cdbfdb5f1ac8781f537ea9acccaed7922349) > Maven home: /opt/homebrew/Cellar/maven/3.9.15/libexec > Java version: 17.0.19, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@17/17.0.19/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.4.1", arch: "aarch64", family: "mac" > > Darwin ****.local 25.4.0 Darwin Kernel Version 25.4.0: Thu Mar 19 > 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 arm64 > > Docker version 29.4.1, build 055a478 > > Gary > > On Mon, May 4, 2026 at 2:19 PM Piotr P. Karwasz > <[email protected]> wrote: > > > > Hi Gary, > > > > On 4.05.2026 14:16, Gary Gregory wrote: > > > I tried to adapt the review kit to my setup, running: > > > > > > sh mvn verify -P docker \ > > > -Prelease artifact:compare \ > > > > > > -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325 > > > > > > Reproducibility likely requires: > > > > export CI=true > > > > This variable toggles the activation of two profiles (`java8-tests` and > > `java8-incompat-fixes`) that allow CI to run tests against a JDK 8 > > toolchain. Unfortunately, it also has some side effects on the generated > > artifacts: > > > > - `jspecify` appears in the `test` scope instead of `provided` scope. > > The artifact is added to the `test` scope by the profile as a workaround > > for a JDK 8 bug, so the SBOMs generated with `CI=true` and `CI=false` > > differ slightly in where `jspecify` appears. > > - For reasons I couldn't fully pin down, the POM files embedded in the > > `*-sources.jar` archive may differ by a comment. The order in which a > > POM-modifying plugin and `maven-source-plugin` execute differs between > > `CI=true` and `CI=false`. > > > > We should almost certainly fix this going forward, for example, by > > running the `deploy-release` workflow without the JDK 8 fixups and > > reserving those for `build` runs[*]. > > > > Piotr > > > > [*] As an aside: the `build` workflow is a misnomer. Its main purpose is > > to run unit tests, and building the artifacts is just a side effect. > > Conversely, the main purpose of `deploy-release` is to build the > > artifacts (without testing) and deploy them to the staging repository. > >
