Switch optional Oracle JDBC driver to the version compiled against Java 17 - #51593
Merged
wilkinsona merged 1 commit intoSep 7, 2026
Merged
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
wilkinsona
added
type: task
wilkinsona
changed the title
Signed-off-by: Fabio Grassi <40345396+fabio-grassi@users.noreply.github.com> See spring-projectsgh-51593
wilkinsona
force-pushed
the
switch-ora-jdbc-to-jdk17
branch
from
September 7, 2026 07:42
5d0fa47 to
b49f9e2
Compare
Member
|
Thank you, @fabio-grassi. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since spring-boot-jdbc requires at least Java 17, it is advisable that the optional dependency from the Oracle JDBC driver points to the version compiled against JDK 17. This PR proposes the following dependency switch:
Please note that this is not a version upgrade in the usual sense and as such apparently it is not covered by the semi-automated process that bumps third party library versions.
See #51570.