To make it more convenient to setup for testing (integration testing) with database vendors which don't upload their JDBC drivers to public repositories, I'm introducing an option to have the build load JDBC drivers from an absolute path.
There will be a new environment variable ADDITIONAL_REPO which you can point to a local directory (use a full path). This directory is expected to have the JDBC drivers.
For example for Oracle I will copy the ojdbc8.jar driver in ~/3rd-party, then I can invoke:
Can't you just put jar to databases/oracle/jdbc (and remove matrix.gradle)? I use it, but I'm not now sure if it's build-in hibernate or in our tooling.
But I can't commit that. So on the CI servers we have the JDBC drivers in a different directory - external to the project - so that people can't download it.