-
Notifications
You must be signed in to change notification settings - Fork 8
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
Run in Java editor fails #80
Comments
I think for the Bazel Run Targets we rely on importing IJ run configurations. @lonhutt do you know if this works with arbitrary |
@guw just FYI (#111 is more important) when I press the Run | Debug on https://github.com/enola-dev/enola/blob/e6240391f16815c0b30e9c0ab10def17aff786e7/tools/hello/src/main/java/dev/enola/common/hello/Hello.java then the Terminal has: cd /home/vorburger/git/github.com/en So it looks like it's not putting anything on the |
It seems to create a new {
"type": "java",
"name": "Hello",
"request": "launch",
"mainClass": "dev.enola.common.hello.Hello",
"projectName": "tools.hello:hello"
} |
When I open code
java_one/
of https://github.com/vorburger/LearningBazel, it opens just fine (see #74).However clicking Run (the gray "hover" thing, of
Run | Debug
) says Build failed, do you want to continue? (from Source: Debugger for Java)There are no related errors in the usual Troubleshooting logs (that I could see).
With this extension, is this a "bug" because @guw this works for you in other projects, or is it "totally expected" and so this just a possible future Frequent Request (FR)?
BTW that Bazel Run Targets tab in the Explorer view is also empty... should there be something there, given the
java_binary(name = "JavaOne", ...
of that small sample project?The text was updated successfully, but these errors were encountered: