Accessibility of runtime_deps and transitive deps

Hey,

We’re (cc: @arifogel) having a heck of a time trying to understand how the IntelliJ plugin handles transitive deps. The issue we’re having is that only direct compile dependencies (hjars for bazel-built or maven jars) are in External Libraries. When we’re debugging, we’re unable to see source code for or set breakpoints in the runtime_deps or the dependencies of our direct compile dependencies.

Adding them to the bazelproject, e.g., targets: @external_project//some/java_library does not make that library indexable.

Is there a different recommended approach to solve this problem?

Thanks!

[ittaiz]

I want to emphasize Brendan’s point- I think this specific issue is not related to blaze/bazel as the issue isn’t external workspaces but debugging transitive deps. Brendan- there isn’t a setting or something to allow loading all transitive deps as external libraries? Sounds like this can be an easy fix which could be only available to Bazel. Wdyt?

[brendandouglas]

We could add that feature to the plugin – JavaWorkspaceImport / JavaSourceFilter is the code which limits which deps are added as libraries.