*nvim-java.txt* For Neovim >= 0.9.4 Last change: 2023 December 13

Table of Contents *nvim-java-table-of-contents*

1. nvim-java |nvim-java-nvim-java|

- Demo |nvim-java-demo|

- Features |nvim-java-features|

- Why |nvim-java-why|

- How to Install |nvim-java-how-to-install|

- Commands |nvim-java-commands|

- APIs |nvim-java-apis|

- How to Use JDK X.X Version? |nvim-java-how-to-use-jdk-x.x-version?|

- Architecture |nvim-java-architecture|

- Projects Acknowledgement |nvim-java-projects-acknowledgement|

1. nvim-java *nvim-java-nvim-java*

Just install and start writing `public static void main(String[] args)`.

DEMO *nvim-java-demo*

FEATURES *nvim-java-features*

- Diagnostics & Auto Completion

- Automatic DAP <https://github.com/mfussenegger/nvim-dap> debug configuration

- Running tests

WHY *nvim-java-why*

- Everything necessary will be installed automatically

- Uses nvim-lspconfig <https://github.com/neovim/nvim-lspconfig> to setup `jdtls`

- Realtime server settings updates is possible using neoconf <https://github.com/folke/neoconf.nvim>

- Auto loads necessary `jdtls` plugins

- Supported plugins are,

- `lombok`

- `java-test`

- `java-debug-adapter`

HOW TO INSTALL *nvim-java-how-to-install*

- Lazyvim <https://github.com/nvim-java/nvim-java/wiki/Lazyvim>

- Install the plugin

Using lazy.nvim <https://github.com/folke/lazy.nvim>

>lua

return {

'nvim-java/nvim-java',

dependencies = {

'nvim-java/lua-async-await',

'nvim-java/nvim-java-core',

'nvim-java/nvim-java-test',

'nvim-java/nvim-java-dap',

'MunifTanjim/nui.nvim',

'neovim/nvim-lspconfig',

'mfussenegger/nvim-dap',

{

'williamboman/mason.nvim',

opts = {

registries = {

'github:nvim-java/mason-registry',

'github:mason-org/mason-registry',

},

},

}

},

}

<

- Setup nvim-java before `lspconfig`

>lua

require('java').setup()

<

- Setup jdtls like you would usually do

>lua

require('lspconfig').jdtls.setup({})

<

Yep! That’s all :)

COMMANDS *nvim-java-commands*

- `JavaDapConfig` - DAP is autoconfigured on start up, but in case you want to force configure it again, you can use this API

- `JavaTestRunCurrentClass` - Run the test class in the active buffer

- `JavaTestDebugCurrentClass` - Debug the test class in the active buffer

- `JavaTestRunCurrentMethod` - Run the test method on the cursor

- `JavaTestDebugCurrentMethod` - Debug the test method on the cursor

- `JavaTestViewLastReport` - Open the last test report in a popup window

APIS *nvim-java-apis*

**DAP**

- `config_dap` - DAP is autoconfigured on start up, but in case you want to force configure it again, you can use this API

>lua

require('java').dap.config_dap()

<

**Test**

- `run_current_class` - Run the test class in the active buffer

>lua

require('java').test.run_current_class()

<

- `debug_current_class` - Debug the test class in the active buffer

>lua

require('java').test.debug_current_class()

<

- `run_current_method` - Run the test method on the cursor

>lua

require('java').test.run_current_method()

<

- `debug_current_method` - Debug the test method on the cursor

>lua

require('java').test.debug_current_method()

<

- `view_report` - Open the last test report in a popup window

>lua

require('java').test.view_last_report()

<

HOW TO USE JDK X.X VERSION? *nvim-java-how-to-use-jdk-x.x-version?*

Neoconf <https://github.com/folke/neoconf.nvim> can be used to manage LSP

setting including jdtls. Neoconf allows global configuration as well as project

vice configurations. Here is how you can set Jdtls setting on `neoconf.json`

>json

{

"lspconfig": {

"jdtls": {

"java.configuration.runtimes": [

{

"name": "JavaSE-21",

"path": "/opt/jdk-21",

"default": true

}

]

}

}

}

<

Pass the settings to Jdtls setup.

>lua

require('lspconfig').jdtls.setup({

settings = {

java = {

configuration = {

runtimes = {

{

name = "JavaSE-21",

path = "/opt/jdk-21",

default = true,

}

}

}

}

}

})

<

ARCHITECTURE *nvim-java-architecture*

Following is the high level idea. Jdtls is the language server nvim-java

communicates with. However, we don’t have all the features we need just in

Jdtls. So, we are loading java-test & java-debug-adapter extensions when we

launch Jdtls. Once the language server is started, we communicate with the

language server to do stuff.

For instance, to run the current test,

- Request Jdtls for test classes

- Request Jdtls for class paths, module paths, java executable

- Request Jdtls to start a debug session and send the port of the session back

- Prepare TCP connections to listen to the test results

- Start nvim-dap and let user interactions to be handled by nvim-dap

- Parse the test results as they come in

- Once the execution is done, open a window show the test results

PROJECTS ACKNOWLEDGEMENT *nvim-java-projects-acknowledgement*

nvim-jdtls <https://github.com/mfussenegger/nvim-jdtls> is a plugin that

follows "Keep it simple, stupid!" approach. If you love customizing things by

yourself, then give nvim-jdtls a try. I may or may not have copied some code

Beautyof Open source!

2. Links *nvim-java-links*

1. *Java*: https://img.shields.io/badge/java-%23ED8B00.svg?style=for-the-badge&logo=openjdk&logoColor=white

2. *Gradle*: https://img.shields.io/badge/Gradle-02303A.svg?style=for-the-badge&logo=Gradle&logoColor=white

3. *Apache Maven*: https://img.shields.io/badge/Apache%20Maven-C71A36?style=for-the-badge&logo=Apache%20Maven&logoColor=white

4. *Neovim*: https://img.shields.io/badge/NeoVim-%2357A143.svg?&style=for-the-badge&logo=neovim&logoColor=white

5. *Lua*: https://img.shields.io/badge/lua-%232C2D72.svg?style=for-the-badge&logo=lua&logoColor=white

Generated by panvimdoc <https://github.com/kdheepak/panvimdoc>

vim:tw=78:ts=8:noet:ft=help:norl: