Open KyleAure opened 2 years ago
Seeing this same behavior with Temurin 17 (build 17.0.4+8) and Temurin 11 (build 11.0.20+8).
Also noticed a couple of path errors when running the signature tests in standalone:
mvn verify -D"test=ee.jakarta.tck.json.bind.signaturetest.jsonb.JSONBSigTest"
Warning: incorrect classpath parameter: C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target/signaturedirectory/jakarta.json.bind-api.jar:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target/jdk-bundle/java.base:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target/jdk-bundle/java.rmi:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target/jdk-bundle/java.sql:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target/jdk-bundle/java.naming (java.nio.file.InvalidPathException: Illegal char <:> at index 112: C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target\signaturedirectory\jakarta.json.bind-api.jar:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target\jdk-bundle\java.base:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target\jdk-bundle\java.rmi:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target\jdk-bundle\java.sql:C:\Users\greg\tck\jakarta-jsonb-tck-3.0.0\jsonb-tck\bin\target\jdk-bundle\java.naming). This directory or jar file will be ignored!
1) The colon :
is being used as a classpath file/directory separator and on Windows it should be a semi-colon instead ;
2) Some of the slashes used in the classpath generation face the wrong way on Windows. They are forward slashes /
and should be back slashes \
.
I think Windows might automatically handle the wrong slash directions, but it would be nice to change to be consistent.
The failure is due to the Signature Test plugin failing to run in
static mode
because it does not recognize or thinks that a specifc argument is missing. This leads it to just output the "Help" message instead of running.Example output:
In the end all the static tests fail, while all the reflective tests run and pass:
I ran the TCK again and forced the TCK to use the Signature Test 1.6 plugin instead of 1.4 and the failure still happens.