Andy Seaborne

Yes - that is weird. Something (tm) put in that width=0.

There's no input shown. What effect is the `.resolveURIs(false)` having? I can't reproduce needing it.

PR #1513 ensures the backup is written atomically. The intermediate files have a name ending ".tmp" and chosen by the JDK library function `Files.createTempFile`.

> Any idea when the next release is due? This is not in 4.6.1 (which is currently in it's VOTE phase). You can get development builds (daily): See https://ci-builds.apache.org/job/Jena/ These...

No cleanup. The PR puts in what the Fuseki engine should do - no hard coded policy. There is no assumption on JVM cleanup. The rest is best done outside...

No code calls the PrefixMapping2 constructors so we can be delete it. It says "Updates go to the local (second) copy only". It is (was) for locally extending prefixes mapping....

> Hm, the advantage of PrefixMapping2 is that the internal 'added' map is again a PrefixMapping and the lookup inherts its performance characteristics. There is a `BufferingPrefixMapping` as well. >...

Let's wait on this one. If Jena uses 2.0.0, it may block downstream still using 1.7.x. slf4j 2.0.0 setup works differently to 1.7 (2.0.0 uses service loaders, 1.7.x has it's...

So the question for Jena upgrading is whether slf4j-api 2.0.0 if jena updates, is compatible with 1.7.x slf4j implementations (client apps using jena). The answer is "no". It looks like...

Slight bump in the road: https://issues.apache.org/jira/browse/LOG4J2-3601 If that is not accepted, each inclusion of log4j-slf4j2-impl needs to be paired with an inclusion of log4j-core.