Dockerfile: explicitly pre-fetch BOM POMs missing from offline Maven cache
The go-offline-maven-plugin and dependency:resolve-plugins do not reliably resolve POM artifacts imported via <scope>import</scope> in <dependencyManagement>. This caused the offline Maven build step to fail with:
Cannot access igniterealtime (...) in offline mode and the artifact
org.junit:junit-bom:pom:5.13.4 has not been downloaded from it before.
Cannot access igniterealtime (...) in offline mode and the artifact
org.mockito:mockito-bom:pom:5.4.0 has not been downloaded from it before.
Add explicit dependency:get calls for junit-bom and mockito-bom alongside the existing plexus-utils workaround, and consolidate all three into a single RUN --mount layer for clarity.
org.opentest4j.AssertionFailedError: expected: not <null>
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
at org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
at org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
at org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
at org.jivesoftware.openfire.session.LocalOutgoingServerSessionTest.outgoingTest(LocalOutgoingServerSessionTest.java:308)
(41 more lines...)