Makes sense as an approach Clearly from prior responses there are large scale users who can’t necessarily migrate immediately so a longer deprecation cycle makes sense
Rob From: Andy Seaborne <a...@apache.org> Date: Friday, 23 May 2025 at 10:57 To: dev@jena.apache.org <dev@jena.apache.org> Subject: Re: Jena 6 On 22/05/2025 21:47, Andy Seaborne wrote: > Removing TDB1 should be a longer deprecation cycle because its > persistent data and also because code deprecation does not show up to > Fuseki configuration file usage. So removal for 6.0.0 looks to me as too > savage. > > We can start with @Deprecated and it does not have to be tied to 6.0.0. > > I'll put in a PR. Its one of the easier ones to do because there are few > code entry points to TDB1. https://github.com/apache/jena/pull/3218 One thing we can do at Jena 6.0.0 is remove the org.apache.jena.tdb package. TDBFactory there has been marked deprecated since 2023-11, and deprecated/forRemoval since 2024-04. All the code is under oaj.tdb1. Classes left in oaj.tdb there are just call throughs to oaj.tdb1. Andy
