I have been converting testing to Junit5 across the Jena modules.
What triggered this is that I found it is possible to set testing up so
that it misses some tests - if JUnit decides to use the JUnit4Provider,
it will not see JUnit5 tests.
JUnit4 to JUnit5 is fairly routine.
Major modules are done and the vintage (Junit4 wrapper) engine removed
from their POMs expect for jena-core. jena-core has JUnit3 as well as
JUnit4 tests, and so needs source code changes to bring it up to JUnit5.
The modules with vintage engine as a test dependency are:
jena-tdb1
jena-text
jena-iri
jena-shex
jena-shacl
jena-geosparql
jena-fuseki2/jena-fuseki-geosparql
jena-fuseki2/jena-fuseki-webapp
jena-extras/jena-commonsrdf
jena-extras/jena-querybuilder
jena-core
jena-benchmarks/jena-benchmarks-jmh
jena-permissions
several of which are going to be retired.
Andy
