Update dependency rules_jvm_external to v6 #20

renovate · 2025-09-21T00:36:04Z

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package	Type	Update	Change
rules_jvm_external	bazel_dep	major	`5.3` -> `6.8`
rules_jvm_external	http_archive	major	`5.3` -> `6.8`

Release Notes

bazelbuild/rules_jvm_external (rules_jvm_external)

`v6.8`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 6.5.0, Bazel 7.6.1 or Bazel 8.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.8")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.28.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.8"
RULES_JVM_EXTERNAL_SHA = "704a0197e4e966f96993260418f2542568198490456c21814f647ae7091f56f2"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.28.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Implement different scope behavior for generated pom files by @vinnybod in bazel-contrib#1336
Add support to outdated for BOMs by @cheister in bazel-contrib#1341
Fix a fatal error when printing verbose logs when dependencies contain exclusions by @vinnybod in bazel-contrib#1342
Use Bazel's JDK to run coursier by @cheister in bazel-contrib#1323
Fix the docs to use the correct tag name by @chrismgrayftsinc in bazel-contrib#1339
Pass boms during (unpinned) coursier fetch by @joca-bt in bazel-contrib#1350
Use copy_file instead of a genrule to link things in the generated workspaces by @shs96c in bazel-contrib#1361
Flip fail_if_repin_required to True by default by @shs96c in bazel-contrib#1371
Avoid spurious warnings about poorly formatted artifact coordinates by @shs96c in bazel-contrib#1374
Prepare for 6.8 release by @sumeetgajjar in bazel-contrib#1380
Add support for gradle resolver by @smocherla-brex in bazel-contrib#1357
Update maven-metadata.xml when publishing locally by @AustinSchuh in bazel-contrib#1369
Ensure root module artifacts and boms take precedence with warnings by @shs96c in bazel-contrib#1373
Allow root module's override tags to take precedence over the overridees from transitive deps. by @sumeetgajjar in bazel-contrib#1381
Modify maven_export to allow exporting zip archives by @AustinSchuh in bazel-contrib#1368
Allow package exclusions and inclusions in javadocs by @vinnybod in bazel-contrib#1293
Allow coursier artifacts to have empty versions provided by BOMs and don't include them in outdated by @cheister in bazel-contrib#1390
[bzlmod] Allow suppressing warning about multiple contributing modules. by @mkosiba in bazel-contrib#1393
Remove dep on android ndk. by @jin in bazel-contrib#1305
Add support for reading artifacts from a file by @shs96c in bazel-contrib#1400

New Contributors

@sumeetgajjar made their first contribution in bazel-contrib#1380
@AustinSchuh made their first contribution in bazel-contrib#1369
@mkosiba made their first contribution in bazel-contrib#1393

Full Changelog: bazel-contrib/rules_jvm_external@6.7...6.8

`v6.7`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 6.5.0, Bazel 7.5.0 or Bazel 8.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.7")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.28.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.7"
RULES_JVM_EXTERNAL_SHA = "a1e351607f04fed296ba33c4977d3fe2a615ed50df7896676b67aac993c53c18"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.28.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Fix docs generation for artifacts with compile only dependencies by @vinnybod in bazel-contrib#1291
Update HEAD to support Bazel 6 -> Bazel 8. by @jin in bazel-contrib#1294
Make multiple modules contributing to the same maven repo namespace warning less verbose and duplicated by @jin in bazel-contrib#1295
Bump robolectric-bazel to 4.14.1.2 by @utzcoz in bazel-contrib#1301
[auth][netrc] Empty account fallback to login by @stevebarrau in bazel-contrib#1299
Fix collection of Maven runtime deps by @fmeum in bazel-contrib#1308
Update protobuf to 29.3 (bzlmod only) by @joca-bt in bazel-contrib#1314
Add support for using Maven BOMs with Coursier by @protocol7 in bazel-contrib#1306
Give the coursier pin alias public visibility to match others by @erikkerber in bazel-contrib#1319
Assume third part of coordinates is a version number by @shs96c in bazel-contrib#1311

New Contributors

@stevebarrau made their first contribution in bazel-contrib#1299
@joca-bt made their first contribution in bazel-contrib#1314
@protocol7 made their first contribution in bazel-contrib#1306

Full Changelog: bazel-contrib/rules_jvm_external@6.6...6.7

`v6.6`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.6")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.26.0",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.6"
RULES_JVM_EXTERNAL_SHA = "3afe5195069bd379373528899c03a3072f568d33bd96fe037bd43b1f590535e7"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.26.0",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Normalise coordinate names by @shs96c in bazel-contrib#1279
Add rules_shell and add loads for sh_binary by @ahumesky in bazel-contrib#1282
fix: Deduplicate deps while amending by @honnix in bazel-contrib#1266
Bump Robolectric to 4.14.1 by @utzcoz in bazel-contrib#1286

Full Changelog: bazel-contrib/rules_jvm_external@6.5...6.6

`v6.5`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.5")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.26.0",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.5"
RULES_JVM_EXTERNAL_SHA = "3a4d56357851cf5b0dae538b3f3e0612a4f58925dfb3cadb2e0c4e87d51e629e"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.26.0",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Fix @rules_kotiln reference in kt_jvm_export by @elwin in bazel-contrib#1263
Do not use or recommend @// labels with Bzlmod by @fmeum in bazel-contrib#1265
pass toolchains to maven_* rules by @elwin in bazel-contrib#1264
Upgrade rules_java and add rule loads by @ted-xie in bazel-contrib#1271
Bump rules_java 7.12.2 and .bazelversion 7.4.0 by @jin in bazel-contrib#1273

New Contributors

@elwin made their first contribution in bazel-contrib#1263
@ted-xie made their first contribution in bazel-contrib#1271

Full Changelog: bazel-contrib/rules_jvm_external@6.4...6.5

`v6.4`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.4")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.4"
RULES_JVM_EXTERNAL_SHA = "85776be6d8fe64abf26f463a8e12cd4c15be927348397180a01693610da7ec90"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Fix the alias generated when using bzlmod and the maven resolver by @shs96c in #1249
Ensure that the pom classifier isn't always downloaded by @shs96c in #1251

Full Changelog: bazel-contrib/rules_jvm_external@6.3...6.4

`v6.3`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.3")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(
    maven,
    "maven",
)

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.3"
RULES_JVM_EXTERNAL_SHA = "c18a69d784bcd851be95897ca0eca0b57dc86bb02e62402f15736df44160eb02"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazelbuild/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Fix TOC entry for bzlmod usage by @jvolkman in #1194
Add a maven.artifact tag example into the bzlmod readme. by @jin in #1195
Update bzlmod.md to remove unpinned_maven by @mbland in #1198
Update bzlmod.md to reflect that gazelle support is now available by @chrismgrayftsinc in #1199
Track whether a repo is pinned or unpinned by explicit attr by @plobsing in #1204
Support plus as repo name delimiter in query-result normalization logic by @plobsing in #1211
Remove repositories attr from maven.artifact by @plobsing in #1202
[Upstream] Add pgp in memory signing support by @ThomasCJY in #1191
handle transitive dependencies of packaging=pom by @mattnworb in #1207
Upgrade rules_java to 7.10.0 by @comius in #1226
Retain comments / licenses in service provider files when merging jars by @vinnybod in #1123
Remove hardcoded javadocopts by @vinnybod in #1212
Add sha256 and sha512 to MavenPublisher by @vinnybod in #1240
Skip non-class files in the exclusions processing for MergeJars by @vinnybod in #1239
Add support for resources in javadoc jars and make variable substitution in javadoc arguments by @vinnybod in #1238
Allow jvm_import to accept a jar parameter by @shs96c in #1242
jvm_import and java_export targets now include a PackageInfo provider @shs96c in #1232

New Contributors

@jvolkman made their first contribution in #1194
@mbland made their first contribution in #1198
@chrismgrayftsinc made their first contribution in #1199
@plobsing made their first contribution in #1204
@ThomasCJY made their first contribution in #1191

Full Changelog: bazel-contrib/rules_jvm_external@6.2...6.3

`v6.2`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.2")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(
    maven,
    "maven",
)

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.2"
RULES_JVM_EXTERNAL_SHA = "808cb5c30b5f70d12a2a745a29edc46728fd35fa195c1762a596b63ae9cebe05"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazelbuild/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Allow runtime deps to be expressed in generated pom.xml files by @vinnybod in #1113
Restore Target Uniqueness Guard in dependency_tree_parser.bzl by @jonshea in #1122
Add support for .netrc on Windows by @bartoszpop in #1127
Use customized repositories for rules_jvm_external's own dependencies by @honnix in #1133
maven_install: fail if 'repositories' attribute is empty by @mattnworb in #1135
Mark maven extension as reproducible by @fmeum in #1141
Propagate testonly attribute to generated plugins by @rdesgroppes in #1142
Pass additional coursier cli options by @honnix in #1137
Remove old comment about grpc-java and bzlmod by @benjaminp in #1143
Fix bzlmod lockfile always not up-to-date by @BoleynSu in #1171
Add RJE_VERBOSE output when a BOM version is overridden by an explicit dependency by @cheister in #1172
Keep BOM's dependencies ordered in the same way they are declared by @cheister in #1176
Allow maven.artifact to have an empty version so it will get its version from a BOM file by @cheister in #1183
Consolidate maven versions of classifiers for an artifact by @cheister in #1179

New Contributors

@bartoszpop made their first contribution in #1127
@honnix made their first contribution in #1133
@mattnworb made their first contribution in #1135
@benjaminp made their first contribution in #1143
@BoleynSu made their first contribution in #1171

Full Changelog: bazel-contrib/rules_jvm_external@6.1...6.2

`v6.1`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.5.0, or Bazel 7 or above.

This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.1")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(
    maven,
    "maven",
)

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.1"
RULES_JVM_EXTERNAL_SHA = "08ea921df02ffe9924123b0686dc04fd0ff875710bfadb7ad42badb931b0fd50"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazelbuild/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

Add manifest_entries to java_export by @shs96c in #1050
Add the ability to pass args to MavenPublisher by @loganasherjones in #937
Do not remove LICENSE files when combining jars by @gkdn in #1054
Support so/dylib/dll packaging types by @dzbarsky in #959
tests for artifact with plus by @gergelyfabian in #1053
Make jvm_import use java from resolved toolchain instead of host machine. by @jin in #1058
Use tool instead of compilation runtime in jvm_import actions by @fmeum in #1059
Fix timout->timeout typo by @brianduff in #1062
fix: determine the version of java correctly by @yesudeep in #1069
Introduce a maven resolver by @shs96c in #989
Remove dev_dependency from rules_android in bzlmod by @erikkerber in #1085
Fixes problem with bom file generation with Bazel 7 by @shs96c in #1079
Remove maven_jar_migrator from MODULE.bazel by @scaiper in #1071
Support use_credentials_from_home_netrc_file via bzlmod extension by @erikkerber in #1089
Index service implementations as well as packages by @illicitonion in #1063
Generate java_plugin targets for annotation processors by @illicitonion in #1102
Remove outdated info from README by @daivinhtran in #1105
Improve repinning performance by not recomputing cache path for every artifact by @BalestraPatrick in #1108
Add an exception for COPYRIGHT and NOTICE files in the same way as LICENSE by @vinnybod in #1107

New Contributors

@loganasherjones made their first contribution in #937
@gkdn made their first contribution in #1054
@dzbarsky made their first contribution in #959
@brianduff made their first contribution in #1062
@yesudeep made their first contribution in #1069
@erikkerber made their first contribution in #1085
@scaiper made their first contribution in #1071
@daivinhtran made their first contribution in #1105
@BalestraPatrick made their first contribution in #1108
@vinnybod made their first contribution in #1107

Full Changelog: bazel-contrib/rules_jvm_external@6.0...6.1

`v6.0`

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.1. If you update and repin your dependencies, your lock file will use the new format.

Usage

This version of rules_jvm_external requires Bazel 5.4.1, Bazel 6.4.0, or Bazel 7 or above.

Bzlmod

If you are using Bazel 7 or above, in your MODULE.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.0")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@&#8203;rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(
    maven,
    "maven",
)

Workspace-based builds

In your WORKSPACE file, add:

load("@&#8203;bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.0"
RULES_JVM_EXTERNAL_SHA = "85fd6bad58ac76cc3a27c8e051e4255ff9ccd8c92ba879670d195622e7c0a9b7"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazelbuild/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@&#8203;rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@&#8203;rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@&#8203;rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.16.1",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)

Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@&#8203;maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

New Contributors

@kotlaja made their first contribution in #933
@daewoongoh made their first contribution in #921
@tirsen made their first contribution in #948
@agluszak made their first contribution in #984
@bertschneider made their first contribution in #1002
@blorente made their first contribution in #996

What's Changed

Requires Java 11 or above
Removed support for jetify
Improved Bazel 7 and bzlmod support
Fix pinning error with Bzlmod by @fmeum in #939
Allow passing sensitive credentials for java_export with environment variables by @thirtyseven in #927
Add classifier_artifacts parameter to java_export to allow users to publish extra artifacts by @thirtyseven in #926
Fix excluded_artifacts for bzlmod by @tirsen in #948
Fix testonly attribute handling by @meteorcloudy in #955
Add compile-only deps to javadocs classpath by @fmeum in #952
javadoc: Allow javadoc targets to reference other javadoc targets by @fmeum in #958
java_export: Fix Make variable substitution by @fmeum in #960
Only print repin warnings if the repin env vars are missing by @shs96c in #975
Normalise timestamps from maven_project_jar with those from java_library by @shs96c in #982
Disable JVM perfdata when stamping jars by @cheister in #988
Handle conflict markers and empty files for the maven_install lock_file parameter by @shs96c in #991
Publish java_export target without sources jar by @bertschneider in #1002
feat(maven_install): Customizable repin instructions by @blorente in #1000
Allow the "raw" version of overridden targets to be used by @shs96c in #994
m2local: solve files not getting resolved by @gergelyfabian in #961
Treat empty files in pinning as if they weren't available by @gergelyfabian in #969
fix: Publish artifacts without additional classifiers by @bertschneider in #1011
Allow the root module to always set the lock file by @shs96c in #1040
Update coursier to v2.1.8 by @cheister in #1042

Full Changelog: bazel-contrib/rules_jvm_external@5.3...6.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Update dependency rules_jvm_external to v6

a0e671f

renovate bot requested a review from snape as a code owner September 21, 2025 00:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update dependency rules_jvm_external to v6 #20

Update dependency rules_jvm_external to v6 #20

Uh oh!

renovate bot commented Sep 21, 2025 •

edited

Loading

Uh oh!

Uh oh!

Update dependency rules_jvm_external to v6 #20

Are you sure you want to change the base?

Update dependency rules_jvm_external to v6 #20

Uh oh!

Conversation

renovate bot commented Sep 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

What's Changed

New Contributors

Usage

Bzlmod

Workspace-based builds

Using dependencies

New Contributors

What's Changed

Configuration

Uh oh!

Uh oh!

renovate bot commented Sep 21, 2025 •

edited

Loading