Could using try-with resources, and moving the http client init into existing try-with blocks), or explicitly closing the clients for tests that use the java http client be useful for Jena6? Autoclosable and some new methods were added in java 21, see https://bugs.openjdk.org/browse/JDK-8304165, so when changing Jena to using two latest LTS, it could be used, instead of waiting for it to handled during GC.
I did some initial experiments and updating the tests looks mostly straightforward, unlike understanding the http client usage within Jena itself, where there is the cache and reuse of clients and usage and reuse of the default client. On Sun, Jun 1, 2025 at 9:22 PM Arne Bernhardt <arne.bernha...@gmail.com> wrote: > +1 for GraphMemValue and renaming GraphMem2* to GraphMem* > > Andy Seaborne <a...@apache.org> schrieb am Fr., 30. Mai 2025, 18:34: > > > Another possible change at Jena6: > > > > Move GraphMem out of the way to GraphMemValue (it is only used to give > > value semantics for the Model API for java datatypes : > > ModelFactory.createDefaultModel. It has been deprecated for awhile). > > > > Then all the "GraphMem2*" can become "GraphMem*". > > > > Andy > > > > >
