Re: spark-core "compile"-scope transitive-dependency on scalatest

I posted a PR; the solution I suggested seems to work (and is simpler than breaking spark-tags into multiple artifacts). On Thu, Dec 15, 2016 at 4:46 PM, Ryan Williams wrote: > ah I see this thread now, thanks; interestingly I don't think the solution > I've proposed here (splitting spark-tags' t

Re: spark-core "compile"-scope transitive-dependency on scalatest

ah I see this thread now, thanks; interestingly I don't think the solution I've proposed here (splitting spark-tags' test-bits into a "-tests" JAR and having spark-core "test"-depend

Re: spark-core "compile"-scope transitive-dependency on scalatest

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 wrote: > spark-core

spark-core "compile"-scope transitive-dependency on scalatest

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 p