Removed references to old v3po plugin 68/3968/1
authorJan Srnicek <[email protected]>
Sun, 27 Nov 2016 11:07:00 +0000 (12:07 +0100)
committerJan Srnicek <[email protected]>
Sun, 27 Nov 2016 11:08:48 +0000 (12:08 +0100)
These(maven part) were causing distribution
export old v3po.json file, which would cause
runtime error due to non-existing keepalive-delay
property

Change-Id: Icde6a8187ff7b1424df18521c2de8279fa7ad33b
Signed-off-by: Jan Srnicek <[email protected]>
nsh/api/pom.xml
nsh/impl/pom.xml
v3po/v3po2vpp/asciidoc/Readme.adoc

index a9688dd..4ef78dd 100644 (file)
@@ -50,7 +50,7 @@
       <artifactId>yang-ext</artifactId>
     </dependency>
     <dependency>
-      <groupId>io.fd.honeycomb.v3po</groupId>
+      <groupId>io.fd.hc2vpp.v3po</groupId>
       <artifactId>v3po-api</artifactId>
       <version>${project.version}</version>
     </dependency>
index 776e0fd..59d9076 100644 (file)
       <version>${project.version}</version>
     </dependency>
     <dependency>
-      <groupId>io.fd.honeycomb.v3po</groupId>
+      <groupId>io.fd.hc2vpp.v3po</groupId>
       <artifactId>v3po2vpp</artifactId>
       <version>${project.version}</version>
     </dependency>
index d9fb563..db779a1 100644 (file)
@@ -32,7 +32,7 @@ Current order of v3po-api writers is:
 
 To find out current order in runtime, turn on logging for writer registry:
 
-  log:set TRACE io.fd.honeycomb.v3po.translate.util.write.registry
+  log:set TRACE io.fd.hc2vpp.v3po.translate.util.write.registry
 
 === Readers
 There is not a strict order for readers, but current configuration produces approx. this order: