I am not sure if this is resolved now - but maven was better at building the assembly jars compared to sbt. To the point where I stopped using sbt due to unpredictable order in which it unjars the dependencies to create the assembled jar (we do have quite a lot of conflicting classes in our dependency tree :-( ). I dont know if this is an artifact of how we specify it in sbt project, or something else ...
If this is still an issue, then using sbt only is a non starter. Regards, Mridul On Fri, Feb 21, 2014 at 9:33 AM, Patrick Wendell <pwend...@gmail.com> wrote: > Hey All, > > It's very high overhead having two build systems in Spark. Before > getting into a long discussion about the merits of sbt vs maven, I > wanted to pose a simple question to the dev list: > > Is there anyone who feels that dropping either sbt or maven would have > a major consequence for them? > > And I say "major consequence" meaning something becomes completely > impossible now and can't be worked around. This is different from an > "inconvenience", i.e., something which can be worked around but will > require some investment. > > I'm posing the question in this way because, if there are features in > either build system that are absolutely-un-available in the other, > then we'll have to maintain both for the time being. I'm merely trying > to see whether this is the case... > > - Patrick
