You're right; we had a discussion here recently about this.
I'll re-open that bug, if you want to send a PR. (I think it's just a
matter of making the scalatest dependency "provided" in spark-tags, if
I remember the discussion.)
On Thu, Dec 15, 2016 at 4:15 PM, Ryan Williams
<ryan.blake.willi...@gmail.com> wrote:
> spark-core depends on spark-tags (compile scope) which depends on scalatest
> (compile scope), so spark-core leaks test-deps into downstream libraries'
> "compile"-scope classpath.
>
> The cause is that spark-core has logical "test->test" and "compile->compile"
> dependencies on spark-tags, but spark-tags publishes both its test-oriented
> and non-test-oriented bits in its default ("compile") artifact.
>
> spark-tags' test-bits should be in a "-tests"-JAR that spark-core can
> "test"-scope depend on (in addition to "compile"-scope depending on
> spark-tags as it does today).
>
> SPARK-17807 was "Not a Problem"d but I don't think that's the right outcome;
> spark-core should not be leaking test-deps into downstream libraries'
> classpaths when depended on in "compile" scope.
>
--
Marcelo
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
