Use Oracle JDBC from maven central #3644
Merged
Conversation
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
shroffk
approved these changes
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The RDB archive (archive engine, data browser retrieval) can use Oracle, MySQL or Posgres JDBC.
For the longest time, Oracle's licensing prevented the Oracle JDBC jar from being available in Maven central.
It had to be downloaded by somebody with an Oracle development network account, and the "install-jar" mechanism then placed it in the local maven repo.
Now that the ojdbc jar is available from maven central, the pom.xml can directly refer to it.
I did add exclusions to only fetch the basic ojdbc jar because none of the existing code needs any of the optional dependencies that would otherwise be added.
Once PBRaw is available online, this would remove the need for "install-jar"
#3637
Checklist
This is a change in build system dependencies. A successful build is a successful test.
It's a change to maven files. Maven has plenty of online material to read which could be called documentation.