lsp-java VS vscode-java

lsp-java mode should handle most of that: https://emacs-lsp.github.io/lsp-java/

Speed of Emacs on Java codebases can be faster than IDEA? With features of lsp-java ? How could it possible~~

I dunno about the netbeans LSP server but I use eclipse JDT language server from Emacs and it works pretty well https://github.com/emacs-lsp/lsp-java

According to lsp-java, variable lsp-java-format-settings-url specifies the url or file path to the eclipse formatter xml settings. This file eclipse-java-google-style.xml works fine in vscode and eclipse. The expected behavior is line longer than 100 is splited to a new line. In spacemacs, split length is still the default 120.

I see that I can configure DAP mode for a new server. This references "java", which I assume points it to dap-java.el within lsp-java.

You should check out emacs-lsp/lsp-java, it's exactly what you want.

Unfortunately I don't use snippets for the settings, but this must be configurable by the client LSP I've already seen people who can do this kind of thing with lsp-java, I wouldn't be surprised if you can also do it with lsp-python.

Can this issue on github help?

More details about the problem over this issue on github: https://github.com/redhat-developer/vscode-java/issues/3060

I've tried Google Java Format, following the settings here,

It seems I actually got it to work in vscode. I found this thread, in which one person told to add: "java.eclipse.downloadSources": true, "java.maven.downloadSources": true, to the settings.json and it seems to work just fine now. Still thanks for your responses :)

Can the retirement version solve the problem? If you are convinced that it is a version of BUG, you can submit a report on GitHub to get official personnel responses.

Good news :) https://github.com/redhat-developer/vscode-java/wiki/Formatter-settings

There is currently no configuration to turn off. If you really need it, you can submit a feature request on GitHub.

-- 💀 "/usr/lib/jvm/java-11-openjdk/", -- or '/path/to/java11_or_newer/bin/java' -- depends on if `java` is in your $PATH env variable and if it points to the right version. "-Declipse.application=org.eclipse.jdt.ls.core.id1", "-Dosgi.bundles.defaultStartLevel=4", "-Declipse.product=org.eclipse.jdt.ls.core.product", "-Dlog.protocol=true", "-Dlog.level=ALL", "-javaagent:" .. home .. "/.local/share/nvim/mason/packages/jdtls/lombok.jar", "-Xms1g", "--add-modules=ALL-SYSTEM", "--add-opens", "java.base/java.util=ALL-UNNAMED", "--add-opens", "java.base/java.lang=ALL-UNNAMED", -- 💀 "-jar", vim.fn.glob( home .. "/.local/share/nvim/mason/packages/jdtls/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar" ), -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ -- Must point to the Change this to -- eclipse.jdt.ls installation the actual version -- 💀 "-configuration", home .. "/.local/share/nvim/mason/packages/jdtls/config_" .. CONFIG, -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^ -- Must point to the Change to one of `linux`, `win` or `mac` -- eclipse.jdt.ls installation Depending on your system. -- 💀 -- See `data directory configuration` section in the README "-data", workspace_dir, }, on_attach = { require("jdtls").setup_dap({ hotcodereplace = "auto" }), require("jdtls.dap").setup_dap_main_class_configs(), }, capabilities = capabilities, -- 💀 -- This is the default if not provided, you can remove it. Or adjust as needed. -- One dedicated LSP server & client will be started per unique root_dir root_dir = root_dir, -- Here you can configure eclipse.jdt.ls specific settings -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request -- or https://github.com/redhat-developer/vscode-java#supported-vs-code-settings -- for a list of options settings = { java = { eclipse = { downloadSources = true, }, configuration = { updateBuildConfiguration = "interactive", }, maven = { downloadSources = true, }, implementationsCodeLens = { enabled = true, }, referencesCodeLens = { enabled = true, }, references = { includeDecompiledSources = true, }, inlayHints = { parameterNames = { enabled = "all", -- literals, all, none }, }, format = { enabled = false, }, }, signatureHelp = { enabled = true }, completion = { favoriteStaticMembers = { "org.hamcrest.MatcherAssert.assertThat", "org.hamcrest.Matchers.*", "org.hamcrest.CoreMatchers.*", "org.junit.jupiter.api.Assertions.*", "java.util.Objects.requireNonNull", "java.util.Objects.requireNonNullElse", "org.mockito.Mockito.*", }, }, contentProvider = { preferred = "fernflower" }, extendedClientCapabilities = extendedClientCapabilities, sources = { organizeImports = { starThreshold = 9999, staticStarThreshold = 9999, }, }, codeGeneration = { toString = { template = "${object.className}{${member.name()}=${member.value}, ${otherMembers}}", }, useBlocks = true, }, }, flags = { allow_incremental_sync = true, }, -- Language server `initializationOptions` -- You need to extend the `bundles` with paths to jar files -- if you want to use additional eclipse.jdt.ls plugins. -- -- See https://github.com/mfussenegger/nvim-jdtls#java-debug-installation -- -- If you don't plan on using the debugger or other eclipse.jdt.ls plugins you can remove this

This is the officially provided extension. if you follow this documentation, still no syntax highlighting, may really be a bug, suggest you file an issue on GitHub.

Try this fix but don't forget VS Code Lombok extension project has not been maintained for long time。