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>
<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>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
- <exclusion>
- <groupId>com.att.aft</groupId>
- <artifactId>dme2</artifactId>
- </exclusion>
</exclusions>
</dependency>
</dependencies>