Natan Silnitsky

I think that there is a key difference between the way bloop optimises builds (caching and pipelining of "large" code modules) and the way "standard, canonical" bazel does it (caching...

@olafurpg sounds interesting. Bazel analyses the build graph and sends each target separate build request to the build tool/server. So now does bloop works well in the limited scope of...

Sorry, I meant does bloop works well in the limited scope of a bazel target (when dependent targets have already been compiled)?

Thank you @olafurpg for the info! How long will cold scala compiler take for a no-op compilation?

Hi @mlachkar, Thank you so much for answering in a detailed manner. The [documentation](https://github.com/scala/docs.scala-lang/blob/main/_overviews/core/collections-migration-213.md#what-are-the-breaking-changes) states that there is a rule called `RoughlyMapValues` for the specific breaking change of `mapValues` returning...

can it be that https://github.com/scala/scala-collection-compat/blob/main/scalafix/rules/src/main/scala/scala/fix/collection/Collection213Roughly.scala just doesn't work?

Maybe [this ](https://github.com/bazelbuild/rules_scala/commit/9171c48cd738152e9b921c52402955843ee8d405) commit surfaced a bug (not sure where), as there is one more level of dependencies... @ittaiz WDYT?

@ittaiz, in this specific case, is the 'problematic' rule`java_import` (`specs2` target)?

@jjudd there are two issues here: 1. missing labels - related to use of java rules which do not yet support label propagation interop with scala rules 2. error in...

by different I mean that maybe the versions `@org_scala_lang_modules_scala_parser_combinators_2_11` and `@org_scala_lang_modules_scala_xml_2_11` are different than the versions of jars that are contained in `scala_repositories` brought by `rules_scala`