Changes to use new Java 11 dbcapi

This bumps the major version and uses the new dbcapi.
BUT it still uses the old alpine base image - until an appropriate replacement is
designated for Java 11

Issue-ID: DMAAP-1363
Signed-off-by: dglFromAtt <dgl@research.att.com>
Change-Id: I9b1aeabc263b3498d801f9af02cdaf059a930525
Signed-off-by: dglFromAtt <dgl@research.att.com>

diff --git a/dbc-client/pom.xml b/dbc-client/pom.xml
index 8c8f1b1..31eb531 100644 (file)
--- a/dbc-client/pom.xml
+++ b/dbc-client/pom.xml
@@ -260,7 +260,7 @@
     <jettyVersion>9.4.12.RC2</jettyVersion>
     <eelf.version>1.0.0</eelf.version>
     <swagger.version>1.5.19</swagger.version>
-    <artifact.version>1.1.8-SNAPSHOT</artifact.version>
+    <artifact.version>2.0.1</artifact.version>
     <!--  SONAR  -->
     <jacoco.version>0.7.7.201606060606</jacoco.version>
     <sonar-jacoco-listeners.version>3.2</sonar-jacoco-listeners.version>

diff --git a/dmaap-bc/pom.xml b/dmaap-bc/pom.xml
index eeff9e8..1c14b5b 100644 (file)
--- a/dmaap-bc/pom.xml
+++ b/dmaap-bc/pom.xml
@@ -29,7 +29,7 @@
   <parent>
     <groupId>org.onap.oparent</groupId>
     <artifactId>oparent</artifactId>
-    <version>2.0.0</version>
+    <version>2.1.0</version>
     <relativePath/>
   </parent>
   <build>
@@ -421,7 +421,7 @@
     <dependency>
       <groupId>org.onap.dmaap.dbcapi</groupId>
       <artifactId>dbcapi</artifactId>
-      <version>1.0.30</version>
+      <version>2.0.1-SNAPSHOT</version>
     </dependency>
   </dependencies>
   <reporting>
@@ -459,7 +459,7 @@
     <jettyVersion>9.4.12.RC2</jettyVersion>
     <eelf.version>1.0.0</eelf.version>
     <swagger.version>1.5.19</swagger.version>
-    <artifact.version>1.1.8-SNAPSHOT</artifact.version>
+    <artifact.version>2.0.1</artifact.version>
     <timestamp>${maven.build.timestamp}</timestamp>
     <maven.build.timestamp.format>yyyy-MM-dd HH:mm</maven.build.timestamp.format>
     <!--  SONAR  -->

diff --git a/pom.xml b/pom.xml
index 85bf520..810e78a 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -29,11 +29,11 @@
   <parent>
        <groupId>org.onap.oparent</groupId>
        <artifactId>oparent</artifactId>
-       <version>2.0.0</version>
+       <version>2.1.0</version>
   </parent>
 
   <properties>
-    <artifactVersion>1.1.8</artifactVersion>
+    <artifactVersion>2.0.1</artifactVersion>
     <multiproject.basedir>${basedir}</multiproject.basedir>
         <docker.maven.plugin.version>1.0.0</docker.maven.plugin.version>
         <skip.docker.build>true</skip.docker.build>

diff --git a/version.properties b/version.properties
index fab1e50..49a923f 100644 (file)
--- a/version.properties
+++ b/version.properties
@@ -25,9 +25,9 @@
 # Note that these variables cannot be structured (e.g. : version.release or version.snapshot etc... )
 # because they are used in Jenkins, whose plug-in doesn't support
 
-major=1
-minor=1
-patch=8
+major=2
+minor=0
+patch=1
 base_version=${major}.${minor}.${patch}
 
 # Release must be completed with git revision # in Jenkins