rules_java
rules_java copied to clipboard
bazelbuild
Java rules for Bazel
The flag docs state: ```# Do not build runfiles symlink forests for external repositories under # `.runfiles/wsname/external/repo` (in addition to `.runfiles/repo`). This reduces runfiles & # sandbox creation times &...
As a coverage tool, it is highly unlikely that a library will include a genuine dependency on `org.jacoco.*`. However; - There are no safeguards in place. If this does happen,...
A bit of background context: I'm trying to upgrade a project running in Bazel 6.5.0 to use more recent versions of, well, everything. Unfortunately, there's a lot of custom stuff...
Cherrypicks: 03add9332a06235e39b9b1968f1236a29d87f7cd Rollforward: Restructure rules_java 01c4009 Remove migration tags pollution in the java_* rules 02df6937cda3f627a47d42391b09b7da0fe3b849 Remove Java proto libraries from rules_java fa37f6120af318849eaf87d1b471e154adf01c61 Rename `java/modules` to `java/common` 000ef3c Stop returning legacy...
New error prone checks since the last java_tools release now break bazel and other downstream projects (https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2430) This is currently blocking a java_tools release (https://github.com/bazelbuild/java_tools/issues/55). I plan to disable the...
[`java_library.srcs`](https://bazel.build/reference/be/java#java_library.srcs) supports `.srcjar` files to facilitate including generated sources. `.properties` files included in `java_library.srcs` are filtered and included in `java_library.resources`. Consider extending the current behaviour so that `.properties` files included...
``` Version: Bazel: 7.2.1 rules_java: 7.1.0 ``` Hi team, we are planning to upgrade our bazel Java version to 21 in two steps, upgrading runtime first, followed by the toolchain...
As far as I can tell, it currently isn't possible to use the output from `--workspace_status_command` in `java_*` rules. Specifically, it seems like a fairly common use-case (and coincidentally, what...
I've been working on extending the BazelTestRunner to add custom metadata (properties) to the JUnit XML generated by Stripe's Java tests, but I'm hitting a roadblock. The most promising approach...
Turbine native image built with default Graal settings fails on Core 2 Duo CPU due to missing instructions: ``` turbine_direct_graal failed: error executing Turbine command (from target @@rules_jvm_external~//private/tools/java/com/github/bazelbuild/rules_jvm_external/zip:zip) external/rules_java~~toolchains~remote_java_tools_linux/java_tools/turbine_direct_graal '-Dturbine.ctSymPath=external/rules_java~~toolchains~remotejdk21_linux/lib/ct.sym'...
