Adds dependency to Derby (without renaming) and also add derbytools dependency #160
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.
Release notes
Fix Derby missed driver classes when built locally for version 10.15.
What does this PR do?
Adds missed Derby jars that contain part of the driver, in particular
derbytools
jar.local_repository
for vendoringjdbc-derby
gems that bundled old Derby driver which made the tests works in the past and hidden the bug of not adding all the Derby jars properly.Why is it important/What is the impact to the user?
Permit to the user to effectively use the locally built Derby driver.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Gemfile
addingand run
Related issues
Logs