logrusx

> I installed the plugin as recommended in [lazy.lua](https://github.com/nvim-java/nvim-java/blob/main/lazy.lua). Nowhere is this referred as recommendation. It's part of lazy.nvim plugin specification and you don't need to copy it. > However,...

> [@logrusx](https://github.com/logrusx) Thanks for the response, I also tried with the starter projects [lazy-java-nvim](https://github.com/nvim-java/starter-lazyvim/tree/main) but the result was the same. Now my configuration looks like this: I don't particularly like...

> I do have the same issue, pinning jdtls version also does not work as it gets ignored That's impossible. How do you pin it?

p.s. @gogbog I'm sorry I didn't sport that last time, but making nvim-lspconfig a dependency of nvim-java and adding opts makes lazy set it up before nvim-java, which causes it...

You need to explicitly call setup. Get rid of opts, it doesn't work with it.

> ahh alright. Pinned it to 1.43 but sadly lombok is still not recognized nor appended to the cmd of jdtls. > > Followed the starter-project (in my case for...

JDTLS is still misconfigured, meaning nvim-java setup didn't run before lspconfig.jdtls.setup. Is there another instance of jdtls? Show me your complete configuration plus :LspInfo Also: > 1.51.0 does also not...

With the rapidly changing ecosystem of Neovim, it's always possible something changed and broke something else. Unfortunately I don't have the time to test one of the starters with vanilla...

[log.log](https://github.com/user-attachments/files/23789746/log.log) This is the line where I pressed the hotkey by mistake that's not into the above log due to the filter: `Nov 25 15:53:37 localhost uwsm[2300529]: Stopping compositor...`

So what you say is hyprshell failed too quickly so systemd prevented it from reaching the point where it can safely load the configuration?