I belive that we don't need mvn settings.

All the maven settings are related to

nexus2 and 3 access, which is not applicable
however these are getting included as part of the
anchor

If they are a dependency they should not be and the job should
be fixed to reflect this.

Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Change-Id: Ia26c05673b8c2069da31bd7e7e7ba63ab4a7621f

diff --git a/jjb/ric-plt-xapp-frame-py/ric-plt-xapp-frame-py.yaml b/jjb/ric-plt-xapp-frame-py/ric-plt-xapp-frame-py.yaml
index e48fbf1..5274db0 100644 (file)
--- a/jjb/ric-plt-xapp-frame-py/ric-plt-xapp-frame-py.yaml
+++ b/jjb/ric-plt-xapp-frame-py/ric-plt-xapp-frame-py.yaml
@@ -19,8 +19,6 @@
     project: ric-plt/xapp-frame-py
     # jenkins job name prefix
     project-name: ric-plt-xapp-frame-py
-    # maven settings file has credentials
-    mvn-settings: ric-plt-xapp-frame-py-settings
     # dont run docs on verify
     tox-envs: code,flake8
     build-node: ubuntu1804-builder-2c-2g