-
Notifications
You must be signed in to change notification settings - Fork 15.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a proto_lang_toolchain for javalite (3.11.x backport) #6976
Add a proto_lang_toolchain for javalite (3.11.x backport) #6976
Conversation
* Add a proto_lang_toolchain for javalite * fix toolchain. Swap javalite example to master repo
The 3.11.1 release process has already started (the protoc for 3.11.1 has already been uploaded to Maven), I'm happy to merge the PR after 3.11.1 release is finished (today/tomorrow), but we don't have a timeline for the next release yet. |
Just being on the release branch is enough. It is easy to point to a commit from Bazel, but pointing to something on master (like #6882) makes it unclear if there will be compatibility issues. |
Bazel was stuck on the javalite branch of protobuf because the master branch was lacking the toolchain necessary for javalite. The fix was backported to 3.11 in protocolbuffers/protobuf#6976
Bazel was stuck on the javalite branch of protobuf because the master branch was lacking the toolchain necessary for javalite. The fix was backported to 3.11 in protocolbuffers/protobuf#6976
Bazel was stuck on the javalite branch of protobuf because the master branch was lacking the toolchain necessary for javalite. The fix was backported to 3.11 in protocolbuffers/protobuf#6976
Bazel was stuck on the javalite branch of protobuf because the master branch was lacking the toolchain necessary for javalite. The fix was backported to 3.11 in protocolbuffers/protobuf#6976
So that javalite can be used from Bazel. Related discussion: #6867
This is a backport of #6882