You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`higherkindness/rules_scala` evolved, in part, from the need for Bazel adoption support for large, monorepo Scala projects.
6
-
Bazel is wonderful because it makes use of parallelism and caching to vastly improve build times. However, to see these benefits, a project must first be broken down into
7
-
tiny packages and make use of fine-grained dependencies. This is not always a realistic short-term goal for large, monorepo Scala projects.
5
+
Previously known as [higherkindness/rules_scala](https://github.com/higherkindness/rules_scala),
6
+
`lucidsoftware/rules_scala` evolved, in part, from the need for Bazel adoption support for large,
7
+
monorepo Scala projects. Bazel is wonderful because it makes use of parallelism and caching to
8
+
vastly improve build times. However, to see these benefits, a project must first be broken down into
9
+
tiny packages and make use of fine-grained dependencies. This is not always a realistic short-term
10
+
goal for large, monorepo Scala projects.
8
11
9
-
`higherkindness/rules_scala` allows for the optional use of Zinc incremental compilation to provide a stepping stone for these projects as they migrate to Bazel.
12
+
`lucidsoftware/rules_scala` allows for the optional use of Zinc incremental compilation to provide a
13
+
stepping stone for these projects as they migrate to Bazel. Although we've verified it to be correct
14
+
and determinisitc, we recommend leaving this disabled, as fine-grained and isolated targets are
15
+
more in-line with the [Bazel philosophy](https://bazel.build/basics/hermeticity).
10
16
11
-
`higherkindness/rules_scala` is written with maintainability and accessibility in mind. It aims to facilitate the transition to Bazel, and to satisfy use cases throughout the Scala ecosystem.
17
+
`lucidsoftware/rules_scala` is written with maintainability and accessibility in mind. It aims to
18
+
facilitate the transition to Bazel, and to satisfy use cases throughout the Scala ecosystem.
12
19
13
20
## Principles
14
21
@@ -17,7 +24,8 @@ tiny packages and make use of fine-grained dependencies. This is not always a re
17
24
3. Be accessible and maintainable.
18
25
4. Have high-quality documentation.
19
26
20
-
If the right design principles are kept, implementing additional features should be simple and straightforward.
27
+
If the right design principles are kept, implementing additional features should be simple and
0 commit comments