Add Windows Terminal ports

[VincentBrodin]

trafficstars

This PR adds three Windows Terminal themes—Bamboo, Bamboo Light, and Bamboo Multiplex.

[s1n7ax]

This would not scan the system to find the available JDKs. So you have to have JDK registered manually as follows. You will get such errors when JDK version defined in gradle not found in the config.

https://github.com/nvim-java/nvim-java?tab=readme-ov-file#clamp-how-to-use-jdk-xx-version

For maven, you might need some modifications:

https://github.com/nvim-java/nvim-java/wiki/Troubleshooting#no_entry-lsp-doesnt-work-on-maven-projects

[AchoVasilev]

I added this to my config:

lspconfig.jdtls.setup({
        settings = {
          java = {
            configuration = {
              runtimes = {
                {
                  name = "Java-17",
                  path = "/usr/bin/java",
                  default = true,
                },
              },
            },
          },
        },
      })

I also tried this path "/usr/lib/jvm/java-17-openjdk-amd64/bin/java", but the result is the same.

[obarbier]

have the same issue. i have 2 jdk (8 and 17) but seem like only 8 is loading up. - would still love some help on this @s1n7ax

Regarding you config one thing I have to say is you should point to the jdk path and not the java executable. i.e. /usr/lib/jvm/java-17-openjdk-amd64/

Also check the LspLog, I am able to solve a lot of my issue from the ERROR log message @AchoVasilev

[AchoVasilev]

This is the LspLog errors.zip It is a pretty long file with errors during build. Also had to change the name to "JavaSE-17". There is a bit of autocompletion and intelli-sense, but I still get the "Import cannot be resolved".

[obarbier]

given that it log say Failed to build workspace. I would delete workspace folder and retry. it is usually under ~/.cache/nvim/jdtls/workspaces/

[AchoVasilev]

Tried it, but still the same error in the logs.

[AchoVasilev]

I added

annotationProcessing = {
                enabled = true
              }

and the error log is now different errors.zip

this is an example project structure:

(module) ├── service1 (module) │ ├── src │ │ │ └── build.gradle ├── service2 (module) │ ├── src │ │ │ └── build.gradle │
└── build.gradle └── settings.gradle

[obarbier]

I do get similar error i just learn to disregard them. I am not familiar with gradle as i mostly use maven. not if some of the issue you are facing are related to this.

Also one thing to note is that you are using multi-module, I haven't found a good flow that work for me. i sort of fix this by using vim.lsp.buf.add_workspace_folder to add all the module folder and that usually work better

[AchoVasilev]

From the nvim-java-core.log I get

[INFO Thu 05 Dec 2024 15:54:12 EET] ...share/nvim/lazy/nvim-java-dap/lua/java-dap/api/setup.lua:80: creating dap configuration for java [DEBUG Thu 05 Dec 2024 15:54:12 EET] ...nvim-java-core/lua/java-core/ls/clients/jdtls-client.lua:62: sending LSP request: workspace/executeCommand [DEBUG Thu 05 Dec 2024 15:54:20 EET] ...nvim-java-core/lua/java-core/ls/clients/jdtls-client.lua:69: workspace/executeCommand success!

So I am guessing that it finds the module correctly? I also cloned this repo https://github.com/jghoman/gradle-subprojects/tree/master and it worked out of the box, without any errors.

[mv-stns]

Wait but what should i do when i dont use build tools like maven or gradle? Packages seem to not work for me... since libraries can be found

[s1n7ax]

@mv-stns https://stackoverflow.com/a/54535301/6202210 Try this. You could use neoconf to have project local jdtls settings. If this works you could add it to tips and tricks in wiki

[mv-stns]

What about packages? im not using any dep managers. unfortunately still not working.

[mv-stns]

Ive clean installed into a empty nvim project and i get this error, i cant find ANY related issues anywhere