aboutsummaryrefslogtreecommitdiffstats
path: root/PolicyEngineUtils/pom.xml
diff options
context:
space:
mode:
authorPamela Dragosh <pdragosh@research.att.com>2018-11-06 19:27:40 -0500
committerPamela Dragosh <pdragosh@research.att.com>2018-11-06 19:27:48 -0500
commitf400382b8a526a23b921818a148e78f0a56da15a (patch)
tree719a5bf5c0c0891c5e65bdd09eb91948d5c5d6bc /PolicyEngineUtils/pom.xml
parent677d872505a8b74a175023ff199b123ff2147dc8 (diff)
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>
Diffstat (limited to 'PolicyEngineUtils/pom.xml')
-rw-r--r--PolicyEngineUtils/pom.xml9
1 files changed, 0 insertions, 9 deletions
diff --git a/PolicyEngineUtils/pom.xml b/PolicyEngineUtils/pom.xml
index 27b91d419..4d552b85f 100644
--- a/PolicyEngineUtils/pom.xml
+++ b/PolicyEngineUtils/pom.xml
@@ -102,11 +102,6 @@
<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>
<exclusions>
@@ -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>