rules_jvm_external
rules_jvm_external copied to clipboard
bazelbuild
Bazel rules to resolve, fetch and export Maven artifacts
If I set up a dependency on a version like "2.0.17+15-d6f2c09b+20230921-1427-SNAPSHOT" (e.g. sbt tends to generate such versions for snapshots), then the coursier generated json (`coursier-deps.json`) contains: ``` "coord": "groupId:artifactId:2.0.17+15-d6f2c09b+20230921-1427-SNAPSHOT",...
When using `maven.install` via bzlmod in the root module, any `bazel_dep` which also uses `maven.install` (with the default repository name) can create duplicate artifacts/conflicts. For instance, when including a bazel_dep...
When a `java_library`, and `java_export` target both have protobuf dependencies, only the `java_library` target successfully builds. The `java_export` target throws the below error for every conceivable class in `com.google.protobuf` ```...
This PR adds (limited) support for bundling AARs for distribution with `maven_publish`. It optimistically uses an `.aar` from `AndroidLibraryAarInfo` as the basis for bundling and then merges the transitive closure...
In one of my projects I am using blzmod with `rules_jvm_external` with `duplicate_version_warning = "error"` and `version_conflict_policy = "pinned"`. When trying to import `contrib_rules_jvm` I get the following error: ```...
Take a JavaFX project with two lockfiles (one for windows and one for linux): ```starlark maven.install( name = "windows", artifacts = [ "org.openjfx:javafx-graphics:win:17", "org.openjfx:javafx-controls:win:17", "org.openjfx:javafx-fxml:win:17", "org.openjfx:javafx-base:win:17", ], lock_file = "//:windows_install.json",...
Hi, I am not really into maven and apoligize for any strange assumption or question. Currently I try to access a local maven repository in our company, there a zip...
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...
Given the following code in a `BUILD` file. ``` load("@rules_jvm_external//:defs.bzl", "java_export") java_export( name = "app-config-lib-export", maven_coordinates = "com.bmuschko.app:config:1.0.0", srcs = glob(["*.java"]), deps = [ "@maven//:org_apache_commons_commons_configuration2" ], runtime_deps = [ "@maven//:commons_beanutils_commons_beanutils"...
Metadata
Owner
Metadata
Bazel rules to resolve, fetch and export Maven artifacts