The DriverManager validates whether the Class returned from the utPLSQL Maven Plugin classloader matches the previously registered driver - they do not as the registered one is an instance living in the Liquibase Plugin classloader and evaluates the permission check to false.runs its static initialisation logic, attempts to register itself with the DriverManager - however as registration is addIfAbsent in DriverManager.registerDriver(.) the Liquibase registered one remains.

The DriverManager attempts to fetch from the current utPLSQL Maven Plugin classloader, it does not yet exist so it provides a fresh one.

The DriverManager sets up and starts looping through the registered drivers (containing the instance of the OracleDriver registered by the Liquibase plugin previously), it then validates whether the caller has permission to load the driver or not using isDriverAllowed(Driver driver, ClassLoader classLoader).

The utPLSQL Maven Plugin starts up and hits DriverManager.getConnection(.).As part of static initialisation in the it registers itself with the DriverManager.Liquibase as part of its run loads the into a child classloader it uses in DatabaseFactory.getConnection(.).Maven spins up a Classloader for the Liquibase Maven Plugin (see )( ).I had the chance to debug a bit further today so as to understand the root cause for the Liquibase + utPLSQL combination issue. I know we can't package ojdbc due to - the utplsql-api is published to We have java-api packaged with maven plugin? That way, users don't need to pull needed package manually into their private (enterprise) repo.

Jdbc no suitable driver found