summaryrefslogtreecommitdiffstats
path: root/jvpp
AgeCommit message (Collapse)AuthorFilesLines
2018-05-24Bump jvpp version from 18.01.1 to 18.01.2Marek Gradzki1-1/+1
Change-Id: I12c7ff2b4381ca07aa7b3f98ce540a67304c76ff Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2018-02-15Bump jvpp version from 18.01 to 18.01.1Marek Gradzki1-1/+1
Change-Id: I406e36fbd9fc039ef78e91dd09d98c1311132514 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2018-01-24Set jvpp version to 18.01Marek Gradzki1-1/+1
Change-Id: Ic240f174140a9739295d8ada2a3e22486ec656f8 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2018-01-22Fix jvpp install scriptsMarek Gradzki2-2/+2
Change-Id: Ia1fdba64b6dacd1cb7c824d5cb34d98face1ec52 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2018-01-10Move jvpp_version file to jvpp dir 1/2Marek Gradzki3-2/+10
Change-Id: I1d7132152561cd8417632ccc16942e2b527f9aa4 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2017-12-19Scripts for installing jvpp jars to local mvn repoMarek Gradzki3-0/+75
By default hc2vpp build downloads latest jvpp packages from nexus.fd.io. They might not be compatible with installed vpp (e.g. in case of non-backward compatible vpp api changes). In order to prevent API mismatch, it is required to use jvpp version corresponding to the vpp installed. The patch includes scripts that can be used before building hc2vpp to install jvpp jars from vpp build dir or vpp-api-java package. Change-Id: I9aa0dc37921e022e5644c54238d3d579f6eb5ba8 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>