-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The following changes have been made: * Following bazel idioms Whereas Buck required the target to be fully qualified, the idiom in Bazel is to omit the specific target within a build file provided that target is the name of the directory. That is `//third_party/java/guava:guava` is the same as `//third_party/java/guava`. Bazel favours brevity. * Minimal visibility Unpicking dependency graphs is a PITA. To avoid accidentally making life hard for ourselves, all targets default to bring private. We only expose a target if it is absolutely required. Public visibility should be vanishingly rare in our build files. * One visible rule per build file Other than breaking cycles in dependency graphs, we should be striving for a single visible target per build file. While this is not a hard-and-fast rule, it makes wiring things up simpler. Typically, this single rule will export anything that should be visible from the file. * Follow seams created by deployable artifacts In the java world, the deployable artifacts are maven jars. By definition, these are public, but for the sake of keeping things under control, we may limit the visibility of them. Despite this, if a library is part of a deployable artifact, then rather than allowing people to depend on the library itself, we should be depending on the deployable artifact. This is why so many targets depend on the remote jar.
- Loading branch information
Simon Stewart
committed
Nov 22, 2018
1 parent
c770b54
commit 2ed1c5e
Showing
28 changed files
with
126 additions
and
180 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.