#696 replaced the DoclingServeApiBuilderFactory SPI with DoclingServeApiProvider and deprecated the old types for removal in 0.7.0, keeping a fallback so existing implementations keep working. This issue tracks removing them.
Before removing
docling-serve-api
docling-serve-client
Both modules
Docs
#696 replaced the
DoclingServeApiBuilderFactorySPI withDoclingServeApiProviderand deprecated the old types for removal in 0.7.0, keeping a fallback so existing implementations keep working. This issue tracks removing them.Before removing
DoclingServeApiProvider.docling-serve-apiai.docling.serve.api.spi.DoclingServeApiBuilderFactory, and itsusesclause inmodule-info.java.DoclingServeApi.DoclingApiBuilderandDoclingServeApi.toBuilder().LegacyProviderAdapterandLegacyProviderAdapterTests.DoclingServeApiProviders: remove the legacy fallback, the warning logged when both SPIs are present, and the "(or of the deprecated …)" part of the no-provider message. UpdateDoclingServeApiProvidersTestsandDoclingServeApiTests.DoclingServeApi.builder(), which describes the fallback.TestApis.StubDoclingServeApi: remove itstoBuilder()override.docling-serve-clientDoclingServeClientBuilderFactoryandDoclingServeClientBuilderFactoryTests. The Jackson detection lives inDoclingServeClient.builder().DoclingServeClientBuilder: dropimplements DoclingApiBuilder<C, B>and the@Overrideannotations of its setters. The setters themselves stay.DoclingServeJackson2Client.toBuilder()andDoclingServeJackson3Client.toBuilder(), which return the concrete builder and aren't deprecated, but drop their@Override.DoclingServeApi.toBuilder()(DoclingServeJackson2ClientTests,DoclingServeJackson3ClientTests,AbstractDoclingServeClientAsyncExecutorTests, which show[removal]warnings today) should useconfig().toBuilder()or the concrete client type.AbstractDoclingServeClientConfigTests.toBuilderKeepsEverySettingandtoBuilderKeepsFollowingRedirectscalltoBuilder()on aDoclingServeClient, which resolves to the deprecatedDoclingServeApi.toBuilder()(warnings suppressed). They test the copy constructor, so they must calltoBuilder()on the concrete client type, notconfig().toBuilder().Both modules
@SuppressWarnings("removal")that only existed for these types, in main and test code.Docs
serve-api-provider-migration.md: remove the Compatibility section on the fallback, or retire the page if it's no longer useful.serve-api.md: remove the "Migrating fromDoclingServeApiBuilderFactory" subsection.CLAUDE.md: remove the mention of the fallback.whats-new.md: add a "Breaking" entry for the removal.