diff options
author | 2016-11-27 12:07:00 +0100 | |
---|---|---|
committer | 2016-11-27 12:08:48 +0100 | |
commit | 8729bc807367eb10b097e7c9fad2ddf85905994a (patch) | |
tree | 862e17330e217ff74f04c308db34513823a14a0c /v3po/v3po2vpp/asciidoc/Readme.adoc | |
parent | f3b25c44e49bb290a30314bea0e6dd21bd4a2b2a (diff) |
Removed references to old v3po plugin
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 <jsrnicek@cisco.com>
Diffstat (limited to 'v3po/v3po2vpp/asciidoc/Readme.adoc')
-rw-r--r-- | v3po/v3po2vpp/asciidoc/Readme.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/v3po/v3po2vpp/asciidoc/Readme.adoc b/v3po/v3po2vpp/asciidoc/Readme.adoc index d9fb563ab..db779a10b 100644 --- a/v3po/v3po2vpp/asciidoc/Readme.adoc +++ b/v3po/v3po2vpp/asciidoc/Readme.adoc @@ -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: |