Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to debug java_binary targets with bazel 0.25 #783

Closed
jordimac opened this issue May 8, 2019 · 1 comment
Closed

Unable to debug java_binary targets with bazel 0.25 #783

jordimac opened this issue May 8, 2019 · 1 comment

Comments

@jordimac
Copy link

jordimac commented May 8, 2019

When using the latest plugin (v2019.04.15) with bazel 0.25, debugging a java_binary fails with:

ERROR: /private/var/tmp/.../external/intellij_aspect/java_classpath.bzl:3:1: file ':intellij_info_impl.bzl' does not contain symbol 'artifact_location'.
ERROR: Extension file 'java_classpath.bzl' has errors.
ERROR: Analysis of aspect '@intellij_aspect//:java_classpath.bzl%java_classpath_aspect of ... failed; build aborted: Extension file 'java_classpath.bzl' has errors.

This is due to the incompatible_no_transitive_loads change in bazel 0.25. bazelbuild/bazel#5636

Workaround is to disable this bazel feature by setting incompatible_no_transitive_loads=false on command line or in .bazelrc

@brendandouglas
Copy link
Contributor

Thanks for letting us know -- I'll fix this upstream, which will land in the release after next.

In the meantime, you can work around this by disabling hotswapping (the only code which uses this aspect), by adding "java.hotswapping.enabled=0" to an ".intellij-experiments' file in your home directory (e.g. ~/.intellij-experiments on linux)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants