Andy Seaborne

Google Guava also has dependencies: ``` [INFO] +- com.google.guava:guava:jar:32.1.3-jre:compile [INFO] | +- com.google.guava:failureaccess:jar:1.0.1:compile [INFO] | +- com.google.guava:listenablefuture:jar:9999.0-empty-to-avoid-conflict-with-guava:compile [INFO] | +- com.google.code.findbugs:jsr305:jar:3.0.2:compile [INFO] | \- com.google.j2objc:j2objc-annotations:jar:2.8:compile ```

Good idea. If the Jena cache abstraction works, the choice can be abstracted away. But the abstraction is basic functionality only without any build control except size. One reason for...

Completed by #2271, #2288 and https://github.com/apache/jena-site/pull/182

See the comment in https://github.com/apache/jena/commit/a56fa1f Code: https://github.com/apache/jena/blob/main/jena-cmds/src/main/java/arq/rdfdiff.java The code has not changed in quite sometime. It's printing the two files. FWIW I think finding a minimal difference of two unordered...

@tomdw Which form/packging of Fuseki are you using? Ensuring `FusekiModule` get triggered for dynamically added datasets will be necessary anyway but maybe the Prometheus code should cope with a changing...

@tomdw Are you running with the Fuseki UI available? Fuseki has forms "webapp" (war file or the jar file in apache-jena-fuseki, or jena-fuseki-full.jar) or "main" (jar file jena-fuseki-server).

Could you rebase this against current main please? The build does not work - it runs into a bug in a dependency that's now been upgraded to a working version.

> - [x] Documentation change and updates are provided for the [Apache Jena website](https://github.com/apache/jena-site/)

Looks great. Tried "vitest --coverage" as well. 😀 Would it be better to have the graph names sorted so they appear in an predicable, albeit arbitrary, order? It can make...

One of the recent dependency updates seems to caused git conflict on package.json and yarn.lock. I *think* the second choice is correct except that `"vitest": "^1.3.1"` in this PR.