-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Platform/toolchain support for Java rules #6521
Comments
Yes! We have a commitment for work early next year. |
CC @hlopko :) |
April '19 update:: I think all three items above are now ready with Also, what's the path for this being available non-experimentally? |
Not as far as I know. We're using it internally and I'm going to flip I think @iirina owns the migration for bazel. |
bazelbuild/bazel#6516 bazelbuild/bazel#6521 RELNOTES: None. PiperOrigin-RevId: 253828017 Change-Id: I15f0295e8759357f481984d361977de2deebac13
bazelbuild/bazel#6516 bazelbuild/bazel#6521 PiperOrigin-RevId: 254374629 Change-Id: I9fd82cbf8d244a0419026b75cfda83894859dbbd
bazelbuild#6516 bazelbuild#6521 PiperOrigin-RevId: 254374629
bazelbuild#6516 bazelbuild#6521 PiperOrigin-RevId: 254374629
This is a duplicate of #4592, closing it in favor of that issue. |
Tracking issue on Bazel Configurability Roadmap
Goal:
The text was updated successfully, but these errors were encountered: