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]>
<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>
<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>
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: