Dan Burkert has posted comments on this change. Change subject: Running kudu-spark tests alone fail finding build dir ......................................................................
Patch Set 2: -Code-Review > I just wanted to make sure that once you pull down the image, if you go > straight into kudu-spark, the build and running the testcases should just > work. Today they don't. This workflow is just not possible with multi-module projects with inter-dependencies, due to maven being broken by design. All builds/tests need to get run from the directory of the top level pom (/java in our case). -- 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: Mladen Kovacevic <mlad...@gmail.com> Gerrit-Reviewer: Todd Lipcon <t...@apache.org> Gerrit-Reviewer: Will Berkeley <wdberke...@gmail.com> Gerrit-HasComments: No
