native-build-tools for Maven might not be working with JUnit 5.13

[michael-simons]

I tried upgrading Neo4j-JDBC to JUnit 5.13, and suddenly native image tests fail:

https://github.com/neo4j/neo4j-jdbc/actions/runs/15384655216/job/43281320390#step:6:416

I See in the release notes that there are known changes:

The JUnit feature in GraalVM Native Build Tools has been rewritten to no longer require JUnit classes to be initialized at build time. Therefore, JUnit’s JARs no longer ship with native-image.properties files that contain --initialize-at-build-time options (introduced in 5.12.0). Please update to the most recent version of GraalVM Native Build Tools prior to upgrading to this version of JUnit

We are already on 0.10.6

https://github.com/neo4j/neo4j-jdbc/blob/main/pom.xml#L184

https://github.com/neo4j/neo4j-jdbc/blob/b10c35bee6be2852063a4aa8d11b7b43057f85d8/neo4j-jdbc-it/neo4j-jdbc-it-cp/pom.xml#L119-L151

After a bit of loud thinking here I took this repository and build todays version locally as 0.11.0-SNAPSHOT and tried my luck with the Neo4j JDBC driver, running the integration tests here as they used to work:

./mvnw -U -DskipClusterIT -Dnative clean verify  -pl neo4j-jdbc-it/neo4j-jdbc-it-cp -am

Using GraalVM 21 it is not quite helpful:

Error: Feature defined by org.graalvm.junit.platform.JUnitPlatformFeature unexpectedly failed with a(n) java.lang.RuntimeException. Please report this problem to the authors of org.graalvm.junit.platform.JUnitPlatformFeature.

Enabling Maven Stacktrace / debug just gives me a pretty useless stacktrace.

GraalVM 24 is more helpful

Error: Feature defined by org.graalvm.junit.platform.JUnitPlatformFeature unexpectedly failed with a(n) java.lang.RuntimeException. Please report this problem to the authors of org.graalvm.junit.platform.JUnitPlatformFeature.
Caused by: java.lang.RuntimeException: Cannot compute test selectors from test ids.
	at org.graalvm.junit.platform.JUnitPlatformFeature.getSelectors(JUnitPlatformFeature.java:147)
	at org.graalvm.junit.platform.JUnitPlatformFeature.beforeAnalysis(JUnitPlatformFeature.java:112)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.lambda$runPointsToAnalysis$0(NativeImageGenerator.java:808)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.FeatureHandler.forEachFeature(FeatureHandler.java:93)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:808)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.doRun(NativeImageGenerator.java:567)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.run(NativeImageGenerator.java:533)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.buildImage(NativeImageGeneratorRunner.java:545)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.build(NativeImageGeneratorRunner.java:732)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.start(NativeImageGeneratorRunner.java:151)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.main(NativeImageGeneratorRunner.java:99)

While @marcphilipp suggested me the full list of classes that used to have to be initialized at build time, I'd rather not go down that route.

Hope you find this useful before a 0.11 release. Thank you!

[dnestoro]

Hey @michael-simons thanks for raising this issue. I reproduced the issue, and i saw that unique-ids file (required for building JUnit test plan) is empty.

Can you just confirm that when you run the tests:

1. there is a directory test-ids in the target directory?
2. inside this directory there should be a file prefixed with junit-platform-unique-ids?
3. that file is empty?

[michael-simons]

Hej :)

JUnit 5.12 + Native image tools 0.10.6 + GraalVM 21:

➜  neo4j-jdbc git:(main) dir neo4j-jdbc-it/neo4j-jdbc-it-cp/target/test-ids                                                  
total 0
92618735 0 drwxr-xr-x   3 msimons  staff   96  6 Jun 15:56 .
92618653 0 drwxr-xr-x  23 msimons  staff  736  6 Jun 15:58 ..
92618736 0 -rw-r--r--   1 msimons  staff    0  6 Jun 15:56 junit-platform-unique-ids-7065398386148287056.txt

empty file

JUnit 5.13 + Native image tools 0.11.0-SNAPSHOT (from yesterday) + GraalVM 21:

✗ dir neo4j-jdbc-it/neo4j-jdbc-it-cp/target/test-ids                                      
total 0
92624082 0 drwxr-xr-x   3 msimons  staff   96  6 Jun 16:04 .
92623999 0 drwxr-xr-x  21 msimons  staff  672  6 Jun 16:04 ..
92624083 0 -rw-r--r--   1 msimons  staff    0  6 Jun 16:04 junit-platform-unique-ids-3382815972320476582.txt

same ;)

[marcphilipp]

I was able to reproduce the problem with NBT 0.10.6 and JUnit 5.13.0 in the neo4j repo. The problem can be solved by adding all the classes from the wiki page linked from JUnit's release notes.

The empty file is written by Maven Surefire because there are no unit tests in that project. There are two additional files written directly in neo4j-jdbc-it/neo4j-jdbc-it-cp/target because the native-maven-plugin currently only configures the output directory for the maven-surefire-plugin but not for the maven-failsafe-plugin that is used here. I've discussed with @dnestoro and he's considering adding support for the maven-failsafe-plugin as well. It used to work because 0.10.6 has a fallback mode (that was activated if the file was empty) which was removed in 0.11.0.

[michael-simons]

I am a very strong proponent that those test cases are integration tests in the best, possible sense, integration testing both my code, database code and GraalVM, so you might not be surprised that I kinda expect this to work with both surefire and failsafe :)

Can I anything else provide ? Happy to test out any further snapshot.

[dnestoro]

Hey @michael-simons I just merged my PR that adds support for maven-failsafe-plugin. Can you please verify that Neo4j-JDBC tests work with current master/snapshot?

[michael-simons]

Will do and report back. Thanks in advance.

[michael-simons]

Lovely result, @dnestoro

Test run finished after 21442 ms
[        59 containers found      ]
[         8 containers skipped    ]
[        51 containers started    ]
[         0 containers aborted    ]
[        51 containers successful ]
[         0 containers failed     ]
[       406 tests found           ]
[         6 tests skipped         ]
[       400 tests started         ]
[         0 tests aborted         ]
[       400 tests successful      ]
[         0 tests failed          ]

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Neo4j JDBC Driver 6.5.2-SNAPSHOT:
[INFO] 
[INFO] Neo4j JDBC Driver .................................. SUCCESS [  7.276 s]
[INFO] Neo4j JDBC Driver (SQL Translation) ................ SUCCESS [  0.168 s]
[INFO] Neo4j JDBC Driver (SQL Translator SPI) ............. SUCCESS [  7.066 s]
[INFO] Neo4j JDBC Driver (SQL Translator reference impl) .. SUCCESS [ 13.789 s]
[INFO] Neo4j JDBC Driver (Spark preparing Translator) ..... SUCCESS [  2.967 s]
[INFO] Neo4j JDBC Driver (Core) ........................... SUCCESS [ 20.183 s]
[INFO] Neo4j JDBC Driver (Integration tests) .............. SUCCESS [  0.138 s]
[INFO] Neo4j JDBC Driver (IT on classpath) ................ SUCCESS [03:23 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:15 min
[INFO] Finished at: 2025-06-23T09:57:30+02:00
[INFO] ------------------------------------------------------------------------

With

diff --git a/pom.xml b/pom.xml
index 995c70cf..7dde5627 100644
--- a/pom.xml
+++ b/pom.xml
@@ -156,7 +156,7 @@
 		<jdbi3.version>3.49.5</jdbi3.version>
 		<jooq.version>3.19.24</jooq.version>
 		<jreleaser-maven-plugin.version>1.18.0</jreleaser-maven-plugin.version>
-		<junit-jupiter.version>5.12.2</junit-jupiter.version>
+		<junit-jupiter.version>5.13.1</junit-jupiter.version>
 		<kotlin-stdlib-jdk8.version>2.1.21</kotlin-stdlib-jdk8.version>
 		<langchain4j.version>1.0.1</langchain4j.version>
 		<license-maven-plugin.version>5.0.0</license-maven-plugin.version>
@@ -181,7 +181,7 @@
 		<micrometer.version>1.15.1</micrometer.version>
 		<mockito.version>5.18.0</mockito.version>
 		<moditect-maven-plugin.version>1.2.2.Final</moditect-maven-plugin.version>
-		<native-maven-plugin.version>0.10.6</native-maven-plugin.version>
+		<native-maven-plugin.version>0.11.0-SNAPSHOT</native-maven-plugin.version>
 		<neo4j-bolt-connection.version>3.0.0</neo4j-bolt-connection.version>
 		<neo4j-cypher-dsl.version>2024.7.0</neo4j-cypher-dsl.version>
 		<neo4j-jdbc.previous.version>6.5.1</neo4j-jdbc.previous.version>

A big thank you to all people involved, including @marcphilipp and @sormuras

[dnestoro]

@michael-simons thanks for testing this!
@marcphilipp thanks for your help as well!