scala_proto_library contains code for all dependencies about rules_scala HOT 7 CLOSED

Any thoughts here? This seems like it could be pretty bad in larger projects? Since the scala_proto_library includes generated code for all of the proto dependencies, if you have a bunch of different proto files with inter-dependencies, you are generating code and compiling it every time those dependencies are used, rather than just sharing the scala library.

from rules_scala.

@andyscott would you have bandwidth to take a look? @bjchambers's points sound valid to me, but I have very limited experience with protobuf

from rules_scala.

The solution for this is to use an aspect that adds granular protoc compilation steps for each small grouping of proto files. It's not terribly hard to implement, so I can take a look this next week.

tweag/rules_haskell has done this for quite some time, and bazelbuild/rules_scala followed suit not too long ago.

from rules_scala.

When balezbuild/rules_scala added that it also broke a lot of the abilities to use ScalaPB extensions (see bazelbuild/rules_scala#753 and bazelbuild/rules_scala#751). I'm also not sure that more granular protoc is necessary.

It seems like an easier fix would be to pass only the protos in srcs to the protoc invocation. Other files in the transitive dep set could be passed using -I. If there is a directory containing only the files to pass, that's easy. I'm not sure if it would be necessary to create a separate directory tree containing all the transitive deps.

from rules_scala.

Any progress / updates?

from rules_scala.

Is there any reason why the fix proposed in #217 doesn't work?

from rules_scala.

Hey @bjchambers sorry about the slow responses; it's a busy time of year. I still must defer to Andy on this one. @andyscott friendly ping : )

from rules_scala.