hvadehra
hvadehra
> Ideally I would prefer to keep the files in tree as "golden" files. That makes sense for the expected output being checked in the test(s), but for the inputs...
It appears that importing this will need a bit of work, I'll do that myself.
> Can this be merged into 7.5.0 ? (or whatever a 7.X release it can go into) That shouldn't be necessary. Once we have a java_tools / rules_java release with...
The java_tools releases have their provenance information embedded in the archives. For eg: if you look at https://github.com/bazelbuild/java_tools/releases/tag/java_v13.9 , download any one of the zip archives and look at the...
I think this just needs to use a java_toolchain that uses the ijar/singlejar tools compiled from source as discussed in the linked issue. So an additional patch with these changes...
> Bazel 7.2.0 now builds successfully and is available as an Alpine package :tada: > specifically bumping abseil-cpp to include their various musl build fixes in newer versions, and the...
@timothyg-stripe Do you have a usecase that specifically needs ijar's zipper tool? See https://github.com/bazelbuild/bazel/issues/19446
I'm not familiar with github actions/cache but I suspect the issue lies there. From the CI run logs, I see it starts with: ``` key: v3-bazel-repo-cache-gcc-8724efc64ec2ae6f9c8726587d03c992069750154b944bc682b0d378f7f9a03c restore-keys: v3-bazel-repo-cache-gcc- ``` and...
Thanks for trying, it was just a shot in the dark :) I presume this issue only occurs on CI, or have you managed to reproduce locally as well? If...