rules_jvm_external
rules_jvm_external copied to clipboard
bazelbuild
Bazel rules to resolve, fetch and export Maven artifacts
So in my project I add an external dependency such as "com.zaxxer:HikariCP:4.0.3" to MODULE.bazel, then i run the command **bazel run @unpinned_maven//:pin** and i don't see my maven_install.json to get...
We have an org-private Artifactory server that we're using with `rules_jvm_external`, and would like to standardize on `.netrc` files for providing credentials. The problem, I've discovered, is that the [`get_home_netrc_contents`](https://github.com/bazelbuild/rules_jvm_external/blob/39dcd72d72769acee2f02b869843259683f346c3/coursier.bzl#L313)...
There are some artifacts that only publish jars with suffixes. I am not sure if that is a good practice or not but I am trying Bazel for our Gradle...
It's not officially part of our public API, but sophisticated users who are attempting to extend `maven_publish` will find this helpful
Some jars include proguard specs in `META-INF/proguard/` `META-INF/com.android.tools` We need to extract these files in order to pass them correctly to R8 for android builds. Normally R8 should detect these...
This is a fix for #914 . SNAPSHOT suffix should not be included in version number. For maven release repository, the artifact path is something like {group}/{artifact}/{version}/{artifact}-{version}. For maven snapshot...
LockFileConverter tries to match the expected path for jar files. It expects the path as "[group]/[artifact]/[version]/[artifact]-[version](-[classifier])(.[extension])". However, when a jar is from a SNAPSHOT version, its version is something like...
Since #737, [MergeJars](https://github.com/bazelbuild/rules_jvm_external/blob/master/private/tools/java/com/github/bazelbuild/rules_jvm_external/jar/MergeJars.java) stopped creating directory entries in the resulting jar if the input jars already contain directory entries. This snippet below creates a minimal reproducing example, in the form...
The COURSIER_OPTS envvar does not work, because it is too early in the command line to be passed to coursier. I'm not sure how to submit a fix to this...
In the context of https://github.com/enola-dev/enola/issues/206, I would like to use the `testonly` support introduced in #346 by @Yannic and @jin. https://github.com/bazelbuild/rules_jvm_external#test-only-dependencies documents how to use it, but in my project...
Metadata
Owner
Metadata
Bazel rules to resolve, fetch and export Maven artifacts