remove scala_library _deploy.jar target about rules_scala HOT 6 CLOSED

Ah. I see why this is necessary at this point, since java_* can't depend onscala_library directly.

from rules_scala.

but can't we solve that with #18 ?

from rules_scala.

Solve the necessity? Yeah, should be able to.

I just meant I see why we can't remove this until there's some other way of depending on scala libs.

from rules_scala.

still they are not "deploy_jars" as such because they don't have the transitive deps, right?

I wonder if fixing that is step 1.

from rules_scala.

Do you mean _deploy.jars for scala_binary or scala_library? Yeah, getting _deploy.jar fixed for scala_binary would be great.

I don't know that getting _deploy.jar working for scala_library is all that useful since the need for those files is really just an artifact of not being able to rely on scala_librarys in java_librarys. They could be called anything and still fill that role. And I don't think in that case that the libraries should be flattened. That sounds dicey/like an antipattern. That's what exports are for, isn't it?

from rules_scala.

this was made implicit (and as such optional) by #61 . It may go away in the future if bazelbuild/bazel#970 is fixed since the only reason they were kept now is to make exporting to java targets easier.

from rules_scala.