The standard incantation -- which is a little different from standard Maven practice -- is:
mvn -DskipTests [your options] clean package mvn [your options] test Some tests require the assembly, so you have to do it this way. I don't know what the test failures were, you didn't post them, but I'm guessing this is the cause since it failed very early on the launcher module and not on some module that you changed. Sean On Fri, Apr 24, 2015 at 7:35 PM, Deborah Siegel <deborah.sie...@gmail.com> wrote: > Hi, > > I selected a "starter task" in JIRA, and made changes to my github fork of > the current code. > > I assumed I would be able to build and test. > % mvn clean compile was fine > but > %mvn package failed > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on > project spark-launcher_2.10: There are test failures. > > I then reverted my changes, but same story. Any advice is appreciated! > > Deb --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
