Remove CLM issues with commons-collections 87/33687/1
authorPamela Dragosh <pdragosh@research.att.com>
Thu, 1 Mar 2018 22:11:20 +0000 (17:11 -0500)
committerPamela Dragosh <pdragosh@research.att.com>
Thu, 1 Mar 2018 22:11:27 +0000 (17:11 -0500)
commitc11d90593b95f03f4b555af0c10ddf3bb2b262c1
treef145c8e67408417751caff7c33d9f06253a9cf91
parentcfe2c6e071f5e43ad01f470a3c87230dd1e1fe13
Remove CLM issues with commons-collections

We know that we are not configuring an LDAP PIP in our
use of the XACML open source. The LDAP implementation
uses Apache Velocity, which uses a very old version
of commons-collections that has security issues. So
we can exclude commons-collections from the build.

Issue-ID: POLICY-504
Change-Id: I6d90731e601f58c8edaca6fe02df30ee2a090c2f
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
controlloop/common/eventmanager/pom.xml
controlloop/common/guard/pom.xml
controlloop/packages/artifacts/pom.xml
controlloop/templates/template.demo/pom.xml