You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Tony Stevenson (JIRA)" <ji...@apache.org> on 2015/01/15 10:07:35 UTC

[jira] [Updated] (SPARK-1181) 'mvn test' fails out of the box since sbt assembly does not necessarily exist

     [ https://issues.apache.org/jira/browse/SPARK-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Stevenson updated SPARK-1181:
----------------------------------
    Reporter: Sean Owen  (was: Sean Owen)

> 'mvn test' fails out of the box since sbt assembly does not necessarily exist
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-1181
>                 URL: https://issues.apache.org/jira/browse/SPARK-1181
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.9.0
>            Reporter: Sean Owen
>              Labels: assembly, maven, sbt, test
>
> The test suite requires that "sbt assembly" has been run in order for some tests (like DriverSuite) to pass. The tests themselves say as much.
> This means that a "mvn test" from a fresh clone fails.
> There's a pretty simple fix, to have Maven's test-compile phase invoke "sbt assembly". I suppose the only downside is re-invoking "sbt assembly" each time tests are run.
> I'm open to ideas about how to set this up more intelligently but it would be a generally good thing if the Maven build's tests passed out of the box.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org