Build DEBUG: message

[krtschil]

I did the following on dev branch after 3.1 merge:

• git pull
• bazel clean --expunge
• bazel build //...
• bazel test //...

Build and test were complete but the build step showed the following info:

Starting local Bazel server (9.1.0) and connecting to it...
DEBUG: /home/klaus/.cache/bazel/_bazel_klaus/737df9514b071507e6718befc284ec9a/external/rules_jvm_external+/private/rules/coursier.bzl:693:18: 
NOTE: rules_jvm_external_deps_install.json was generated by an older version of rules_jvm_external and needs to be regenerated. 
To update, run 'bazel run @rules_jvm_external_deps//:pin'.

The suggested command failed:

bazel run @rules_jvm_external_deps//:pin
ERROR: No repository visible as '@rules_jvm_external_deps' from main repository

Something to worry about or is this expected?

[tameware]

It worries me! I've not seen it before. I'll try to reproduce.

[tameware]

I needed the --expunge step, then was able to reproduce.

I'll ask Cursor to look into it.

[tameware]

Innocuous, per Cursor. Where should we note this to avoid raising the same concern in the future?

The build succeeded. The DEBUG line and the failed pin command are separate issues, and neither blocks your work.

What the DEBUG line means

This comes from rules_jvm_external’s own internal Maven lockfile, not from anything in the dds repo:

rules_jvm_external_deps_install.json was generated by an older version of rules_jvm_external

Your project uses rules_jvm_external only for java_export in jni/BUILD.bazel (Maven jar packaging). You do not have a maven.install() block or your own maven_install.json. The lockfile in question lives inside the rules_jvm_external 7.0 module (see its MODULE.bazel).

It’s a NOTE at DEBUG level — informational only. The build completed with 1929 actions and no errors.

Why bazel run @rules_jvm_external_deps//:pin failed

That command is meant for maintainers of rules_jvm_external, not consumers. Under Bzlmod:

• The repo is internal to the module (canonical name like rules_jvm_external++maven+rules_jvm_external_deps)
• @rules_jvm_external_deps is not visible from your main repo, so Bazel reports: No repository visible as '@rules_jvm_external_deps'

The suggested command assumes a WORKSPACE-style setup where you own that Maven repo. That doesn’t apply here.

What you should do

Nothing. Safe to ignore unless the log noise bothers you.

If you ever add your own Maven dependencies, you’d set up something like this in MODULE.bazel:

maven = use_extension("@rules_jvm_external//:extensions.bzl", "maven")
maven.install(
    name = "maven",
    artifacts = [...],
    lock_file = "//:maven_install.json",
)
use_repo(maven, "maven")

Then repin with:

REPIN=1 bazel run @maven//:pin

That’s for your dependencies, not for fixing the upstream rules_jvm_external_deps notice.

To quiet DEBUG output (optional):

bazel build //... --ui_event_filters=-debug

Summary: Build is fine. The message is upstream noise from rules_jvm_external 7.0’s bundled lockfile. The pin command fails because you’re not meant to run it from a consumer repo.

[krtschil]

This message also appears when you do a fresh git clone and bazel build //...