Todd Lipcon has posted comments on this change. Change subject: Running kudu-spark tests alone fail finding build dir ......................................................................
Patch Set 2: I forget: do we already have an easy way to override the "search for binaries" from the command line? maybe we should just make the error/exception message nicer when it can't find the binaries, like: "Could not auto-detect location of Kudu binaries in build tree. To explicitly set a location, set $KUDU_BIN_DIR in your environment or ensure that the kudu server binaries are on your $PATH" or whatever. That should satisfy the ability to develop Java-ecosystem components and run the tests using a kudu-client in m2 so long as you have a working Kudu install on your system. -- To view, visit http://gerrit.cloudera.org:8080/4630 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ib452086cf57a3cb4249bb7c1f91c7572e55466ce Gerrit-PatchSet: 2 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Mladen Kovacevic <mlad...@gmail.com> Gerrit-Reviewer: Dan Burkert <d...@cloudera.com> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Todd Lipcon <t...@apache.org> Gerrit-Reviewer: Will Berkeley <wdberke...@gmail.com> Gerrit-HasComments: No
