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

I'm trying to add maven local repository under `maven_install` but seems like it doesn't support this currently. What I did is ``` maven_install( name = "mvn", artifacts = [ #...

type: feature request
coursier-cli

Bazel 1.1.0 started warning about sha128 uses, which has pushed me to switch to `rules_jvm_external` from `rules_maven`. Am I doing something wrong, or is Bazel now unable to give useful...

type: feature request

This was motivated by a conversation with @simonstewart for better developer ergonomics and gradual adoption, because this is what Maven and Gradle users are used to. The general idea is...

type: feature request

Assume there is a maven package with the following dependency chain (`

type: feature request

With our maven_install.json it takes about 10-20 seconds to parse the JSON. Bazel just added a JSON parser so if this package switched to it, that bottleneck would go away....

type: feature request

e.g. for this repo, there are 7 `maven_install` external repositories: ``` //external:unpinned_unsafe_shared_cache_with_pinning //external:unpinned_regression_testing //external:unpinned_policy_pinned_testing //external:unpinned_maven_install_in_custom_location //external:unpinned_maven //external:unpinned_manifest_stamp_testing //external:unpinned_json_artifacts_testing ``` Running `@rules_jvm_external//pin` runs the `:pin` target on every single one of...

cla: yes

Seen javadoc process consuming lots of cpu&mem, also just a matter of being able to customize what's exported. Disabling should disable not only publishing but also building sources/javadocs.

The more I look into it, one of the biggest pitfalls of Bazel in JVM projects is the dependencies management. While this project is awesome and does help with that...

Running `@maven//:outdated` (which is otherwise quite amazing) gets a bit noisy when some artefacts in use have pre-release versions. For example: ``` androidx.annotation:annotation [1.1.0 -> 1.2.0-alpha01] ``` I don't know...

Aloha! We are currently running into issues with conflicting class path bindings, for an application that's depending on both `ch.qos.logback:logback-classic` and `org.apache.avro:avro-tools`. For example, we're seeing this: ``` SLF4J: Found...

type: feature request