[
https://issues.apache.org/jira/browse/SPARK-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283941#comment-14283941
]
Sean Owen commented on SPARK-4442:
----------------------------------
[~matthewcornell] Normally I'd say you don't need to build any JARs yourself,
and shouldn't bother manually managing JARs; just use Maven or SBT and write in
the dependencies you want. But I see that Spark doesn't actually publish test
artifacts. (Which to be fair would be unusual. But [~joshrosen] is that not the
simplest way to expose this?).
You can "mvn package" as shown on the Building Spark documentation, and you'll
end up with a bunch of artifacts in core/target, including the test JAR file
containing Spark's test code and thus any utility code you want from there.
> Move common unit test utilities into their own package / module
> ---------------------------------------------------------------
>
> Key: SPARK-4442
> URL: https://issues.apache.org/jira/browse/SPARK-4442
> Project: Spark
> Issue Type: Improvement
> Reporter: Josh Rosen
> Priority: Minor
>
> We should move generally-useful unit test fixtures / utility methods to their
> own test utilities set package / module to make them easier to find / use.
> See https://github.com/apache/spark/pull/3121#discussion-diff-20413659 for
> one example of this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
