Did you check docs and existing issues?

• I have read all the plugin docs
• I have searched the existing issues
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.11.2

Operating system/version

ManjaroLinux

Describe the bug

The nvim-java plugin still hasn't been updated to properly support Mason v2.0. As a result, language server management is broken or inconsistent.

Additionally, in the spring-boot.nvim plugin, autocomplete does not work for application.yaml and .properties files. These are key configuration files in Spring Boot projects, so this limits the usefulness of the plugin in real-world development.

Please look into updating compatibility for Mason v2.0 and fix the missing autocomplete in Spring Boot config files.

Steps To Reproduce

Steps to Reproduce

1. Install nvim-java and spring-boot.nvim using a modern Neovim setup (e.g. lazy.nvim or packer.nvim).

2. Ensure you're using Mason v2.0+.

3. Open any Spring Boot project.

4. Try to use :Mason or install Java LSP (like jdtls) through Mason — it doesn't properly integrate due to outdated plugin support.

5. Open application.yaml or application.properties.

6. Start typing Spring Boot configuration keys.

7. Expected behavior: Autocompletion suggestions should appear.

8. Actual behavior: No suggestions appear, even though the plugin is loaded.

Expected Behavior

nvim-java should fully support Mason v2.0, allowing seamless installation and management of Java language servers like jdtls.

In spring-boot.nvim, when editing application.yaml or application.properties, autocompletion should suggest valid Spring Boot configuration keys based on the current context and metadata.