Move dmaap dependency to parent

Dmaap is already used in 3 repositories, and we anticipate
more. So let's define our usage in parent.

I am also upgrading to the release by Dmaap team for
Casablanca. Let's cross our fingers they fixed a couple of
license issues.

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

diff --git a/integration/pom.xml b/integration/pom.xml
index 065ddb7..1cbe1ab 100644 (file)
--- a/integration/pom.xml
+++ b/integration/pom.xml
@@ -36,6 +36,7 @@
         <maven.compiler.source>1.8</maven.compiler.source>
         <maven.compiler.target>1.8</maven.compiler.target>
         <version.logback>1.2.3</version.logback>
+        <version.dmaap>1.1.8</version.dmaap>
     </properties>
 
     <distributionManagement>
@@ -130,6 +131,13 @@
                 <artifactId>logback-classic</artifactId>
                 <version>${version.logback}</version>
             </dependency>
+            
+            <!-- Dmaap Client -->
+            <dependency>
+                <groupId>org.onap.dmaap.messagerouter.dmaapclient</groupId>
+                <artifactId>dmaapClient</artifactId>
+                <version>${version.dmaap}</version>
+            </dependency>
 
             <!-- Client library for Cambria event routing API -->
             <dependency>