Upgrade dmaap client with security fix

Dmaap removed security issues.

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

diff --git a/pom.xml b/pom.xml
index eba1c04..5338855 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -67,7 +67,7 @@
 
                <!-- Project common dependency versions -->
                <jetty.plugin.version>9.2.3.v20140905</jetty.plugin.version>
-               <dmaap.version>1.0.0</dmaap.version>
+               <dmaap.version>1.1.3-SNAPSHOT</dmaap.version>
                <httpclient.version>4.5.5</httpclient.version>
                <jackson.version>2.9.4</jackson.version>
                <commons.fileupload.version>1.3.3</commons.fileupload.version>
@@ -107,31 +107,6 @@
                </site>
        </distributionManagement>
 
-        <repositories>
-                <!-- LF repositories -->
-                <repository>
-                        <id>ecomp-releases</id>
-                        <name>Release Repository</name>
-                        <url>${nexusproxy}/content/repositories/releases/</url>
-                </repository>
-                <repository>
-                        <id>ecomp-staging</id>
-                        <name>Staging Repository</name>
-                        <url>${nexusproxy}/content/repositories/staging/</url>
-                </repository>
-                <repository>
-                        <id>ecomp-snapshots</id>
-                        <name>Snapshots Repository</name>
-                        <url>${nexusproxy}/content/repositories/snapshots/</url>
-                </repository>
-                <repository>
-                        <id>ecomp-public</id>
-                        <name>Public Repository</name>
-                        <url>${nexusproxy}/content/repositories/public/</url>
-                </repository>
-                <!-- LF repositories END-->
-        </repositories>
-
        <reporting>
          <plugins>
            <plugin>