Remove exclusion of dme

Since upgrading to dmaap 1.1.9, the exclusion is no
longer needed. This exclusion may have been the culprit
to POLICY-698's problem. Thus, removing the added
dependency that was put in to resolve it.

This should now clear all the javax.jms inclusions
which have license issues.

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

diff --git a/PolicyEngineUtils/pom.xml b/PolicyEngineUtils/pom.xml
index 27b91d4..4d552b8 100644 (file)
--- a/PolicyEngineUtils/pom.xml
+++ b/PolicyEngineUtils/pom.xml
@@ -101,11 +101,6 @@
             <groupId>com.google.code.gson</groupId>
             <artifactId>gson</artifactId>
         </dependency>
-        <dependency>
-            <groupId>com.att.aft</groupId>
-            <artifactId>dme2</artifactId>
-            <version>3.1.200</version>
-        </dependency>
         <dependency>
             <groupId>org.onap.dmaap.messagerouter.dmaapclient</groupId>
             <artifactId>dmaapClient</artifactId>
@@ -114,10 +109,6 @@
                     <groupId>org.slf4j</groupId>
                     <artifactId>slf4j-log4j12</artifactId>
                 </exclusion>
-                <exclusion>
-                    <groupId>com.att.aft</groupId>
-                    <artifactId>dme2</artifactId>
-                </exclusion>
             </exclusions>
         </dependency>
     </dependencies>