cheister
cheister
In our codebase we're using the [MapStruct annotation processor](https://github.com/mapstruct/mapstruct/tree/main) which can print out a lot of warnings for unmapped target properties when the annotation processors are run. Using javac_options with...
After updating to version 1.7.1 with Bazel 5.1.0 I get the error ``` ERROR: src/test/java/BUILD:8:13: in kt_jvm_test rule //src/test/java:KtTest: Traceback (most recent call last): File "cache/bazel/879c5fa76919d0bed49168a2e457a904/external/io_bazel_rules_kotlin/kotlin/internal/jvm/impl.bzl", line 306, column 32,...
Currently the json output for fetch gives no indication that an artifact was renamed. e.g. ``` > coursier fetch --json-output-file dep-tree.json org.apache.commons:commons-io:1.3.2 /Users/cheister/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/commons-io/commons-io/1.3.2/commons-io-1.3.2.jar > cat dep-tree.json | python -m json.tool...
When updating to Bazel 7.0.0 the default [Build without the Bytes (BwoB) setting](https://blog.bazel.build/2023/10/06/bwob-in-bazel-7.html) goes from `--remote_download_all` to `--remote_download_toplevel`. For our build, this started breaking the intermediate jars used by rules_jvm_external...
Don't print test output for regular build. ``` bazel build //... DEBUG: rules_jvm_external/private/lib/coordinates.bzl:85:18: Assuming com.android.support:appcompat-v7:aar:28.0.0 should be interpreted as com.android.support:appcompat-v7:28.0.0@aar DEBUG: rules_jvm_external/private/lib/coordinates.bzl:85:18: Assuming com.android.support:appcompat-v7:aar:28.0.0 should be interpreted as com.android.support:appcompat-v7:28.0.0@aar DEBUG:...
Allow Rails 8.x and Ruby 3.4