There is an 'ojdbc-bom' v21 already included with groupId 'com.oracle.database.jdbc' covering all jars listed explicitly for v19.3 here (excluding ojdbc10).
Check out the content of Oracle's Maven bom here: https://repo1.maven.org/maven2/com/oracle/database/jdbc/ojdbc-bom/21.1.0.0/ojdbc-bom-21.1.0.0.pom
Also see Oracle's announcements: https://medium.com/oracledevs/all-in-and-new-groupids-oracle-jdbc-drivers-on-maven-central-a76d545954c6 https://blogs.oracle.com/developers/post/oracle-database-client-libraries-for-java-now-on-maven-central
The com.oracle.ojdbc version management was originally introduced in: #18242
Comment From: snicoll
This can't really be a task as it is a user-facing change that should end up in the changelog.
Comment From: wilkinsona
I've used enhancement for this sort of issue in the past. See https://github.com/spring-projects/spring-boot/issues/26574, for example.
Comment From: snicoll
There is an 'ojdbc-bom' v21 already included with groupId 'com.oracle.database.jdbc' covering all jars listed explicitly for v19.3 here
This is a noteworthy change as users relying on the old groupId won't get dependency management anymore and should upgrade to toe com.oracle.database.jdbc groupId.