Github user afs commented on the issue:
https://github.com/apache/jena/pull/401
I've tried out the PR and it passes the build and Fuseki starts up. I
renamed the ServiceLoader files as `org.apache.jena.sys.JenaSubsystemLifecycle`
(I have a script for that now,I can do that after the PR is merged).
One other change is class `system.JenaInit` => `...system.jenaSystem` for
compatibility.
This is the JDI version, not the "speculative thought" above. That works,
but does risk changing initialization order between jena-arq and jena-core
which is the most sensitive part of initialization. That does not cause
problems in the test suite but deployed applications are a big unknown. Given
the risks and impacts, I'm currently inclined to go straight to the change to
`META-INF/services/org.apache.jena.sys.JenaSubsystemLifecycle`.
Putting in an adapter `org.apache.jena.system.JenaSubsystemLifecycle` ends
up as replicating the machinery to find services.
It's a bit bumpy for people working from development - we can let them know
via dev@ that they need to do a clearup and rebuild.
So - looking good!
---
