salesforce/bazel-eclipse

Classpath containers empty in Bazel 6.0

guw opened this issue · 1 comments

guw commented

Interesting discovery. With Bazel 6.0 the aspect JSON output changed.

Example project:
https://github.com/salesforce/bazel-jdt-java-toolchain

5.1.1:

    "key": {
        "aspect_ids": [
            "@bazeljavasdk_aspect//:bzljavasdk_aspect.bzl%bzljavasdk_aspect"
        ],
        "label": "//compiler/third_party/turbine:turbine_direct"
    },

6.0.0:

    "key": {
        "aspect_ids": [
            "@bazeljavasdk_aspect//:bzljavasdk_aspect.bzl%bzljavasdk_aspect"
        ],
        "label": "@//compiler/third_party/turbine:turbine_direct"
    },

Question is .... Is this an intended change, i.e. does BEF need to deal with it or is this something that needs to be fixed in the aspects?