This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Upgrading Bazel to 3.0.0 #3510
Merged
Upgrading Bazel to 3.0.0 #3510
Conversation
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 was referenced Apr 14, 2020
Closed
Closed
Closed
This was referenced Apr 15, 2020
Closed
Before this `scripts/travis/test.sh` was not working when run in a container.
nwangtw
approved these changes
Apr 16, 2020
nicknezis
added a commit
that referenced
this pull request
Sep 14, 2020
* Bazel 3.0.0 * Updated to use `rules_jvm_external` * Buildozer cleanup
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the Bazel build scripts to use this new capability: https://github.com/bazelbuild/rules_jvm_external
The goal would be to better manage the project's dependencies and not have to manually update the various transitive dependencies. This tool will use a dependency's pom.xml to dynamically generate the Bazel targets for each of the dependencies.
This approach started with the buildozer migration which did a lot of formatting cleanup, but ultimately didn't work. After the buildozer cleanup, I had to manually update the WORKSPACE and BUILD files to use the new maven_install feature.