HONEYCOMB-61: Move vpp context model to v3po-api

Change-Id: I92d9cdd199e245adf5d22ff9756e05d82d66abc4
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>

diff --git a/v3po/vpp-translate-utils/src/main/yang/naming-context.yang b/v3po/api/src/main/yang/naming-context.yang
similarity index 91%
rename from v3po/vpp-translate-utils/src/main/yang/naming-context.yang
rename to v3po/api/src/main/yang/naming-context.yang
index 0bcfc09..aa4ced2 100644 (file)
--- a/v3po/vpp-translate-utils/src/main/yang/naming-context.yang
+++ b/v3po/api/src/main/yang/naming-context.yang
@@ -11,7 +11,6 @@ module naming-context {
             "Initial revision.";
     }
 
-    // TODO This should become part of v3po-api as operational-only data
     container contexts {
 
         list naming-context {

diff --git a/v3po/vpp-translate-utils/pom.xml b/v3po/vpp-translate-utils/pom.xml
index ee931c5..cc87e16 100644 (file)
--- a/v3po/vpp-translate-utils/pom.xml
+++ b/v3po/vpp-translate-utils/pom.xml
@@ -34,6 +34,11 @@
             <artifactId>translate-utils</artifactId>
             <version>${project.version}</version>
         </dependency>
+        <dependency>
+            <groupId>${project.groupId}</groupId>
+            <artifactId>v3po-api</artifactId>
+            <version>${project.version}</version>
+        </dependency>
         <dependency>
             <groupId>io.fd.vpp</groupId>
             <artifactId>jvpp</artifactId>