Skip to content

Conversation

@marschall
Copy link
Contributor

Deprecate Derby support since Apache Derby is retired since 2023.

Closes gh-36042

Deprecate Derby support since Apache Derby is retired since 2023.

Closes spring-projectsgh-36042

Signed-off-by: Philippe Marschall <philippe.marschall@gmail.com>
@marschall marschall marked this pull request as draft December 18, 2025 10:23
@sbrannen sbrannen added the in: data Issues in data modules (jdbc, orm, oxm, tx) label Dec 18, 2025
@marschall
Copy link
Contributor Author

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 only main code for removal, no tests. I had to add @SuppressWarnings to main code using deprecated Derby code for the build to work.

I did one small semi-related change, I replaced OutputStreamFactory.getNoopOutputStream() with OutputStream.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?

@bclozel bclozel added this to the 7.1.x milestone Dec 18, 2025
@bclozel bclozel added the type: enhancement A general enhancement label Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecate Derby support since Apache Derby is retired since 2023

3 participants