Refactor unit test data

There were many copies of test policies and examples
strewn through the Apex unit tests. This change cleans
up the unit tests so that a single version of all example
policies is used in all tests.

Also added a new relative file root command line parameter
to Apex to allow the root of relative paths in configuration
files to be set.

Apologies for the size of this review but unfortunately
all of this must be done in one shot.

Issue-ID: POLICY-1252
Change-Id: Ibbb18fbf18e3897a1c61301d0a65e62bc643a0e9
Signed-off-by: liamfallon <liam.fallon@ericsson.com>
223 files changed
tree: ee2f3a8e543c31993c51a58257354ccffb648dfe
  1. auth/
  2. client/
  3. context/
  4. core/
  5. docs/
  6. examples/
  7. model/
  8. packages/
  9. plugins/
  10. services/
  11. src/
  12. testsuites/
  13. tools/
  14. .gitignore
  15. .gitreview
  16. BUILD.adoc
  17. docker_build.sh
  18. docker_merge.sh
  19. docker_verify.sh
  20. INFO.yaml
  21. LICENSE.txt
  22. pom.xml
  23. README.md
  24. version.properties
README.md

Copyright (C) 2016-2018 Ericsson. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy APEX PDP Engine code. The settings file only needs to support the standard Maven repositories (e.g. central = http://repo1.maven.org/maven2/), and any proxy settings needed in your environment.

To build it using Maven 3, run: mvn clean install