summaryrefslogtreecommitdiffstats
path: root/jvpp
AgeCommit message (Collapse)AuthorFilesLines
2018-01-22Fix jvpp install scriptsMarek Gradzki2-2/+2
Change-Id: Ia1fdba64b6dacd1cb7c824d5cb34d98face1ec52 Signed-off-by: Marek Gradzki <mgradzki@cisco.com> (cherry picked from commit c4c23ef02f8f8a4198637458ebf8558d778bfa49)
2018-01-11Bump jvpp version to 18.04-SNAPSHOTMarek Gradzki2-2/+2
Also sets version of vpp package dependencies to 18.04. Change-Id: I0b3faf6418ce9055ad05da41ba4fb022992f3784 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>