Deprecate Derby support since Apache Derby is retired since 2023 #36042
Description
From the Apache Derby project site
On 2025-10-10, the Derby developers voted to retire the project into a read-only state. Derby development and bug-fixing have ended. No further releases will be published. The Derby website and wiki are frozen in place. Derby JIRA issues are now read-only and new bugs cannot be logged. The user and developer lists are disabled and can be accessed only through their archives.
The last Apache Derby release was on 14 November 2023. We should probably first deprecate and the remove Derby support. Maybe log a warning when Derby is detected.
A quick search shows the following affected code places:
org.springframework.jdbc.core.metadata.DerbyCallMetaDataProviderorg.springframework.jdbc.core.metadata.DerbyTableMetaDataProviderorg.springframework.jdbc.core.metadata.CallMetaDataProviderFactory#DERBYorg.springframework.jdbc.core.metadata.DerbyEmbeddedDatabaseConfigurerorg.springframework.jdbc.core.metadata.TableMetaDataProviderFactoryorg.springframework.jdbc.datasource.embedded.EmbeddedDatabaseConfigurersorg.springframework.jdbc.datasource.embedded.EmbeddedDatabaseTypeorg.springframework.jdbc.core.StatementCreatorUtilsorg.springframework.orm.jpa.vendor.Database#Derby
I can work an a PR if there is agreement.