With release 8.0.31 of the jdbc connector / driver for mysql the artifact mysql:mysql-connector-java:jar:8.0.31 has been relocated to com.mysql:mysql-connector-j:jar:8.0.31: MySQL Connector/Jartifacts moved to reverse-DNS compliant Maven 2+ coordinates. This also changes the name of the jar file containing the jdbc driver from mysql-connector-java.jar to mysql-connector-j.jar.
The corresponding virtual schema (in this case mysql-virtual-schema) must use the correct jar name in two places
With release 8.0.31 of the jdbc connector / driver for mysql the artifact mysql:mysql-connector-java:jar:8.0.31 has been relocated to com.mysql:mysql-connector-j:jar:8.0.31: MySQL Connector/Jartifacts moved to reverse-DNS compliant Maven 2+ coordinates. This also changes the name of the jar file containing the jdbc driver from
mysql-connector-java.jar
tomysql-connector-j.jar
.MySQLVirtualSchemaIntegrationTestSetup.JDBC_DRIVER_NAME
settings.cfg
settings.cfg
provided as static resourceContent of static resource
src/test/resources/settings.cfg
:mysql-virtual-schema will therefore replace the resource by a string generated dynamically with to contain the correct name of the jar file:
The current ticket additionally requests to create tickets for all JDBC based virtual schemas to follow this pattern, too.