-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
bug: DAP config not found - multimodule projects #169
Comments
A previous workaround mentioned adding a new file to the root level. This ended up reloading the whole project, but after the reloading had completed there was a significant performance impact when using it normally to navigate a file and you were still not able to set a breakpoint. |
@s1n7ax I run some tests using this repository and I believe issue is that, the project workspace directory is not unique (There is an open issue in nvim-java-core project releted to this). I used this branch during the tests. ( the AstroVim java pack use this way to generate unique worksapce folder) |
This is fixed now: nvim-java/nvim-java-core#54 |
@s1n7ax same question.
When I open nvim in the project root directory, the directory tree is normal. Maybe should check
but no work. |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.9.5
Operating system/version
MacOS 14.4.1
Describe the bug
Very similar to this closed issue, however a colleague of mine and I are not able to run enable the debugger. I noticed this when I started opening a file in our java project (built w/ maven) and all things were functioning normally, however breakpoint would not be set when I hit
space db
. Then doingspace dc
said"No configuration found for
java
. You need to add configs todap.configurations.java
(See:h dap-configuration
)"Two more interesting things to note
:JavaRunnerRunMain
it returnsConfig not found
Previous resolution suggested to pull latest version, but installed freshly (using these steps) today (April 25 2024). As previous contributor suggested on the original issue, this issue still seems to exist for multimodule projects.
Steps To Reproduce
1.) Install following these instructions.
2.) Open a java file in a java project, specifically a test file.
3.) use hotkey
space db
to add a breakpoint (or manual command) and observe nothing happens.Expected Behavior
to see breakpoint set on line where debug breakpoint hotkey was keyed in.
The text was updated successfully, but these errors were encountered: