Use policy/parent mariadb version

Use the same version of mariadb across policy repositories.
This will also clear a license issue, albeit a false
positive.

Issue-ID: POLICY-1061
Change-Id: I4267975518fe9efce9530db687a2cfd3bf872641
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>

diff --git a/pom.xml b/pom.xml
index de5b85a..26a040c 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -66,7 +66,6 @@
         <logback.version>1.2.3</logback.version>
         <junit.version>4.12</junit.version>
         <eclipselink.version>2.7.0</eclipselink.version>
-        <mariadb.jdbc.version>2.1.0</mariadb.jdbc.version>
         <hibernate.core.version>5.2.10.Final</hibernate.core.version>
         <hibernate.commons.annotations.version>5.0.1.Final</hibernate.commons.annotations.version>
         <commons.io.version>2.5</commons.io.version>
@@ -191,11 +190,6 @@
                 <artifactId>org.eclipse.persistence.jpa</artifactId>
                 <version>${eclipselink.version}</version>
             </dependency>
-            <dependency>
-                <groupId>org.mariadb.jdbc</groupId>
-                <artifactId>mariadb-java-client</artifactId>
-                <version>${mariadb.jdbc.version}</version>
-            </dependency>
             <dependency>
                 <groupId>org.hibernate</groupId>
                 <artifactId>hibernate-core</artifactId>