rules_jvm_external icon indicating copy to clipboard operation
rules_jvm_external copied to clipboard

Bazel rules to resolve, fetch and export Maven artifacts

Results 259 rules_jvm_external issues
Sort by recently updated
recently updated
newest added

**Background** The export rule only supports `gpg_sign` option which requires the `gpg` binary to be installed on the machine and set up correctly. This doesn't fit the need if we...

**Background** Address issue https://github.com/bazelbuild/rules_jvm_external/issues/1190 Maven central requires OpenPGP signatures for all the artifacts. Gradle did it through the [signing plugin](https://docs.gradle.org/current/userguide/signing_plugin.html#using_in_memory_ascii_armored_openpgp_subkeys). In Bazel jvm rule the only existing support is using...

Specifically, the maven.install invocation quite rightly warns you when some dependent module has requested a different version than you, but gives you no tools to solve the problem. Perhaps it...

There's two use cases I'm trying to account for here. 1. I need to add resources to the javadoc jar such as a `LICENSE` file. 2. I need to send...

Necessary to avoid loading the `@bazel_tools//tools/android` package, which relies on bind()s to work, which rules_android HEAD has deleted.

Using the examples in the documentation, consider the following setup: ```python # MODULE.bazel bazel_dep(name = "rules_jvm_external", version = "6.1") maven = use_extension("@rules_jvm_external//:extensions.bzl", "maven") maven.artifact( artifact = "grpc-core", exclusions = ["io.grpc:grpc-util"],...

When using bzlmod, if you invoke maven.override( name = "repo1", coordinates = "foo.bar:baz", target = "//foo/bar:baz", ) and then invoke maven.install twice: maven.install( name = "repo1", ... ) maven.install( name...

In Artifactory, we have a repository called `maven` and inside maven, we can assume we have a library under `maven/my/org/my-library/0.3.0-SNAPSHOT`. In this index, we have the following files: - maven-metadata.xml...

The `maven_export` rule and the corresponding `MavenPublisher` application only support basic auth using username/password. This does not work for repositories which use token-based auth. The most common example of this...

We might be doing a maven.artifact for a coordinate that is coming from a BOM with the same version. Would be nice to get a warning that tells me to...