Update dependency rules_jvm_external to v6 #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.3
->6.6
Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
bazelbuild/rules_jvm_external (rules_jvm_external)
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
@//
labels with Bzlmod by @fmeum in https://github.com/bazel-contrib/rules_jvm_external/pull/1265New Contributors
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
alias
generated when usingbzlmod
and themaven
resolver by @shs96c in https://github.com/bazelbuild/rules_jvm_external/pull/1249pom
classifier isn't always downloaded by @shs96c in https://github.com/bazelbuild/rules_jvm_external/pull/1251Full 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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
maven.artifact
tag example into the bzlmod readme. by @jin in https://github.com/bazelbuild/rules_jvm_external/pull/1195jvm_import
to accept ajar
parameter by @shs96c in https://github.com/bazelbuild/rules_jvm_external/pull/1242jvm_import
andjava_export
targets now include aPackageInfo
provider @shs96c in https://github.com/bazelbuild/rules_jvm_external/pull/1232New Contributors
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
pom.xml
files by @vinnybod in https://github.com/bazelbuild/rules_jvm_external/pull/1113rules_jvm_external
's own dependencies by @honnix in https://github.com/bazelbuild/rules_jvm_external/pull/1133maven
extension as reproducible by @fmeum in https://github.com/bazelbuild/rules_jvm_external/pull/1141testonly
attribute to generated plugins by @rdesgroppes in https://github.com/bazelbuild/rules_jvm_external/pull/1142New Contributors
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:What's Changed
manifest_entries
tojava_export
by @shs96c in https://github.com/bazelbuild/rules_jvm_external/pull/1050java
from resolved toolchain instead of host machine. by @jin in https://github.com/bazelbuild/rules_jvm_external/pull/1058jvm_import
actions by @fmeum in https://github.com/bazelbuild/rules_jvm_external/pull/1059New Contributors
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:To add dependencies, later in your
MODULE.bazel
file:Workspace-based builds
In your
WORKSPACE
file, add:Then, later in your
WORKSPACE
file, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazel
file, reference the targets directly:New Contributors
What's Changed
jetify
bzlmod
supporttestonly
attribute handling by @meteorcloudy in https://github.com/bazelbuild/rules_jvm_external/pull/955javadoc
targets to reference otherjavadoc
targets by @fmeum in https://github.com/bazelbuild/rules_jvm_external/pull/958Full 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: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.