Not sure but I use sbt/sbt ~compile instead of package. Any reason we use package instead of compile(which is slightly faster ofc.)
Prashant Sharma On Thu, Apr 24, 2014 at 1:32 PM, Patrick Wendell <pwend...@gmail.com> wrote: > This is already on the wiki: > > https://cwiki.apache.org/confluence/display/SPARK/Useful+Developer+Tools > > > > On Wed, Apr 23, 2014 at 6:52 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > > I'm just asked by others for the same question > > > > I think Reynold gave a pretty helpful tip on this, > > > > Shall we put this on Contribute-to-Spark wiki? > > > > -- > > Nan Zhu > > > > > > Forwarded message: > > > > > From: Reynold Xin <r...@databricks.com> > > > Reply To: d...@spark.incubator.apache.org > > > To: d...@spark.incubator.apache.org <d...@spark.incubator.apache.org> > > > Date: Thursday, February 6, 2014 at 7:50:57 PM > > > Subject: Re: Is there any way to make a quick test on some pre-commit > > code? > > > > > > You can do > > > > > > sbt/sbt assemble-deps > > > > > > > > > and then just run > > > > > > sbt/sbt package > > > > > > each time. > > > > > > > > > You can even do > > > > > > sbt/sbt ~package > > > > > > for automatic incremental compilation. > > > > > > > > > > > > On Thu, Feb 6, 2014 at 4:46 PM, Nan Zhu <zhunanmcg...@gmail.com(mailto: > > zhunanmcg...@gmail.com)> wrote: > > > > > > > Hi, all > > > > > > > > Is it always necessary to run sbt assembly when you want to test some > > code, > > > > > > > > Sometimes you just repeatedly change one or two lines for some failed > > test > > > > case, it is really time-consuming to sbt assembly every time > > > > > > > > any faster way? > > > > > > > > Best, > > > > > > > > -- > > > > Nan Zhu > > > > > > > > > > > > > > > > > > > > > > >
