Overall I think this would be a good idea. The main blocker is just that I think the Maven build is much slower right now than the SBT build. However, if we were able to e.g. parallelize the test build on Jenkins that might make up for it.
I'd actually like to have a trigger where we could tests pull requests with either one. - Patrick On Fri, Oct 24, 2014 at 1:39 PM, Hari Shreedharan <hshreedha...@cloudera.com> wrote: > Over the last few months, it seems like we have selected Maven to be the > "official" build system for Spark. > > > I realize that removing the sbt build may not be easy, but it might be a good > idea to start looking into that. We had issues over the past few days where > mvn builds were fine, while sbt was failing to resolve dependencies which > were test-jars causing compilation of certain tests to fail. > > > As a first step, I am wondering if it might be a good idea to change the PR > builder to mvn and test PRs consistent with the way we test releases. I am > not sure how technically feasible it is, but it would be a start to > standardizing on one build system. > > Thanks, > Hari --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
