rules_jvm
rules_jvm copied to clipboard
Contributed Bazel rules that make working with java projects more pleasant
all in the title, this https://github.com/bazel-contrib/rules_jvm/blob/main/java/test/com/github/bazel_contrib/contrib_rules_jvm/javaparser/generators/workspace/com/gazelle/java/javaparser/generators/AnnotationFromJavaStandardLibrary.java is waaaaaaay too long on windows... error in kokoro (using our bazel based build of google/or-tools for windows): `WORKSPACE`: ``` git_repository( name = "contrib_rules_jvm",...
We split our maven dependencies into multiple maven install rules to make adding/upgrading etc deps easier. It looks like the gazelle plugin here only supports a single maven install rule....
spotbugs takes a list of jars to use as plugins. It would be nice to be able to specify targets to use in the spotbugs rule to add to that...
Currently this always generates the following rules when a `proto_library` rule is present: ``` java_proto_library( name = "my_java_proto", deps = [":my_proto"], ) java_library( name = "my_java_library", visibility = ["//:__subpackages__"], exports...
- [x] Create `MODULE.bazel` file and e2e test in this repo - [x] Setup the Publish-to-BCR app and publish a release to the Bazel Central Registry - [ ] Provide...
For the most part, resolving dependencies by packages works pretty well and the cases where it does not aren't hard to workaround, however, there's one use case I found where...
Hi is there any thought / interest in adding kotlin support to the gazelle extension? Have briefly started to look at the changes required and curious if its on others...
Bazel will natively create a `test.xml` for all test runners if they do not create one themselves. For the checkstyle test-runner it would create a test.xml that captures the system-out....
Fix for https://github.com/bazel-contrib/rules_jvm/issues/285 With a [ParameterizedTest](https://junit.org/junit5/docs/5.0.2/api/org/junit/jupiter/params/ParameterizedTest.html) it is possible to generate test case names with invalid XML characters. E.g. ``` @ParameterizedTest @ValueSource(strings = {"Weird\bname"}) void testFoo(String input) { ... }...
I am currently using your java_junit5_test to set up Cucumber/Gherkin test that are build using Bazel. Although the tests operate like they should, they both give me a warning displayed...