Deprecate Derby support#36045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Draft

marschall wants to merge1 commit intospring-projects:main

base:main

Choose a base branch

frommarschall:deprecate-derby

Draft

Deprecate Derby support#36045

marschall wants to merge1 commit intospring-projects:mainfrommarschall:deprecate-derby

+23 −3

Conversation

Copy link

Contributor

marschall commentedDec 18, 2025

Deprecate Derby support since Apache Derby is retired since 2023.

Closesgh-36042

Deprecate Derby support

17f5737

Deprecate Derby support since Apache Derby is retired since 2023.Closesspring-projectsgh-36042Signed-off-by: Philippe Marschall <philippe.marschall@gmail.com>

marschall marked this pull request as draft

December 18, 2025 10:23

sbrannen added the in: dataIssues in data modules (jdbc, orm, oxm, tx) label

Dec 18, 2025

Copy link

ContributorAuthor

marschall commentedDec 18, 2025

Draft since main is still 7.0.

I did no log any warnings when Derby support is used. I'm not aware of such a thing being done anywhere today, let me know if I should add it.

I marked onlymain code for removal, no tests. I had to add@SuppressWarnings tomain code using deprecated Derby code for the build to work.

I did one small semi-related change, I replacedOutputStreamFactory.getNoopOutputStream() withOutputStream.nullOutputStream().org.springframework.jdbc.datasource.embedded.OutputStreamFactory now has no users left, we could deprecate it as well.

The checked in documentation still mentions Derby in quite a few places, let me know if I should remove it from there.

I believe this should go to the 7.1 changelog. I did find a changelog checked in. Are these manually maintained?