bazel: Strict deps infraction passes when it should fail- regression in 0.12.0-RC1

Description of the problem / feature request:

Bazel 0.12.0-RC1 (built from https://github.com/bazelbuild/bazel/commit/b33e5afa313322a7048044c44d854cbb666b988e) passes a strict deps infraction using rules_scala scala_import when it correctly fails it on 0.11.1

BUILD.bazel:

package(default_visibility = ["//visibility:public"])
load(
    "@io_bazel_rules_scala//scala:scala_import.bzl",
    "scala_import",
)

java_library(
    name = "leaf",
    srcs = ["Leaf.java"],
    deps = [":scala_import_transitive"],
)

#failure only on 0.11.1 bazel
java_import(
    name = "scala_import_transitive",
    jars = [],
    deps = [
        ":logback_scala_import",
    ],
)

scala_import(
    name = "logback_scala_import",
    jars = [
        "logback-classic-1.1.11.jar",
    ],
)

#failure on both 0.11.1 bazel and 0.12.0-rc1
java_import(
    name = "java_import_transitive",
    jars = [],
    deps = [":logback_java_import"],
)

java_import(
    name = "logback_java_import",
    jars = [
        "logback-classic-1.1.11.jar",
    ],
)

Bugs: what’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

run bazel build on this [repo](repro: https://github.com/ittaiz/strict-deps-false-positive/tree/master ) with 0.11.1 and see it fail, then run it with the above bazel binary and see it pass

What operating system are you running Bazel on?

mac os

Any other information, logs, or outputs that you want to share?

I haven’t been able to drill down and figure out if this is a scala_import issue or a java-skylark issue. Might be relevant to add I’m also witnessing false negative issues with strict deps where it prints out warnings for direct dependencies. Still working on an isolated repro for that