Hi, this is follow-up to the discussion started on the last VPP weekly meeting.
In my opinion, the biggest advantages are: 1) it would make VPP build faster and more stable 2) it would make possible to use build system that supports dependency management and hence is more suitable for java build (e.g. Maven or Gradle) Having 2) we could for example translate vpe.api to yang (messages as RPCs), generate Java bindings (requires yangtools from ODL) and have NETCONF support in HC for all VPP APIs. The jVpp project could have two parts: - Java API generator that could be referenced from outside (e.g. in form of a maven plugin) - actual API generation for all the plugins that live in VPP codebase, other fd.io plugins (e.g. NSH) could be also included or use API generator. Regards, Marek
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
