Remove CLM issues with commons-collections 97/33697/1
authorPamela Dragosh <pdragosh@research.att.com>
Thu, 1 Mar 2018 23:00:06 +0000 (18:00 -0500)
committerPamela Dragosh <pdragosh@research.att.com>
Thu, 1 Mar 2018 23:00:16 +0000 (18:00 -0500)
commitcaead0115fa286d6796ad749464e8df09f383338
tree70ad5bb9eed2948a46f0a8e041187aa9fdbd3407
parent96787c49cd192096916e482e5b55e91652de3817
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-507
Change-Id: I735eae4fe507ad016d9b0b49e67536415edb9820
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
ONAP-PDP/pom.xml
ONAP-XACML/pom.xml