-
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
Move Java runfiles library out of Bazel #24394
Conversation
@hvadehra The CI failures on this PR look like they shouldn't be related to my changes, did something else change? |
This is still a work in progress, please hang on / wait for the final release. |
Should go through in #24391 |
784f8a2
to
dafc984
Compare
@hvadehra Had to fix one more test, CI is green now. |
@fmeum resolve conflicts please? |
c90618f
to
e1703a0
Compare
As it turns out, this is not so easy to import. There is a divergence between the internal BUILD files and one's being changed here. Also the (deleted) files are still used internally, and simply pointing them to the internal @meteorcloudy Thoughts? |
@comius who also mentioned a complex import for the c++ lib. |
Hmm, eventually we do want to use the runfiles library from rules_java both internally and externally, right? If this is not going to make it for Bazel 8, we should probably spend some time on untangling the copybara setup? |
Work towards bazelbuild/bazel#24394 PiperOrigin-RevId: 700322638 Change-Id: Ic8af8b0bb8ad82f0e89c87b3ccb84d44b89067c5
Work towards bazelbuild/bazel#24394 PiperOrigin-RevId: 700325236
Work towards bazelbuild/bazel#24394 PiperOrigin-RevId: 700325236
Work towards bazelbuild/bazel#24394 PiperOrigin-RevId: 700586193
Work towards #24394 PiperOrigin-RevId: 700624807 Change-Id: Iaca87f49b1fdad090ef00eef0828f60ca30f4e55
Work towards #24394 PiperOrigin-RevId: 700652158 Change-Id: I94709ef8cee7ce358ff1e13430ebe33d0be7b249
@bazel-io flag |
(for 8.1.0) |
@bazel-io fork 8.1.0 |
It is off topic, but can we also kill JAVA_RUNFILES during the process? There is a TODO to kill it but nobody did it yet. |
Yes, we should, but that affects all runfiles libraries as well as Bazel itself. I would say that getting rid of |
No description provided.