0.2.0

What's Changed

• Removed a custom progress report capability because eclipse.jdt.ls now
  implements the standard progress report mechanism. Note that in versions before
  1.18.0 of eclipse.jdt.ls the progress report implementation caused issues. If
  you're on an earlier version of eclipse.jdt.ls you may want to stick to
  nvim-jdtls 0.1

• Adjusted the log path used in :JdtShowLogs to account for a change in
  Neovim 0.8

• Improved the handling of multiple LSP clients, both non-jdtls clients like
  null-ls, but also of multiple jdtls clients if many projects are open in the
  same Neovim instance.

• Added a :JdtHotcodeReplace command that allows to trigger code replacement
  while debugging manually.

• If a user provides config.capabilities in the start_or_attach call, the
  capabilities are now extended with the default client capabilities ((from
  lsp.protocol.make_client_capabilities()) so users can provide only the
  additions instead of having to provide all of them.

• Added a super_implementation function which allows to jump to the super
  implementation of a method under the cursor.

• :JdtCompile now only shows errors from jdtls instead of showing all
  diagnostic errors.

• Fixed an issue that prevented the "Extract to local variable (replace all
  occurrences)" code action from working and added a extract_variable_all
  function to make it possible to bind the action to a keymap.

• Changed some error messages to provide hints on how to resolve the errors.

• Buffers for JDK or third party libraries (jdt:// URLs) have now
  buftype=nofile set to avoid issues with Neovim features like swap files.

New Contributors

• @figsoda made their first contribution in #318
• @lidulibai made their first contribution in #324
• @magidc made their first contribution in #338
• @fengwk made their first contribution in #350