unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Editing Java (with LSP)
Date: Mon, 13 Jun 2022 22:32:23 +0200	[thread overview]
Message-ID: <87bkuw5mp4.fsf@zamazal.org> (raw)
In-Reply-To: 87k09ky8kc.fsf@gmail.com

>>>>> "AB" == Alessandro Bertulli <alessandro.bertulli96@gmail.com> writes:

    AB> Does any of you write Java code?  How is it? Do you have the
    AB> same problems too? If yes, have you found a solution? Do you use
    AB> LSP?

I use lsp-mode relatively successfully to work on a Java project with
~9000 *.java files (https://github.com/oVirt/ovirt-engine).  I find it
easier than using lsp-mode with C because no special compiler
arrangements are needed, it works itself.  I needn’t to use anything
else.  The only special configuration I use is

  (setq lsp-java-vmargs
        '("-noverify" "-Xmx4G" "-XX:+UseG1GC"
          "-XX:+UseStringDeduplication"))

but I can’t recall why it is needed.

From time to time, I experience similar symptoms like those you
describe.  In such a case, I delete ~/.emacs.d/.cache and
~/.emacs.d/eclipse.jdt.ls.  Then it fetches jdtls, reindexes the project
and starts working fine again.

OTOH, dap-mode works much worse and I cannot use it for Java debugging.
IIRC the most annoying thing was collapsing expanded data structures all
the time, making practically impossible watching what happens with data.
And the overall functionality was limited due to inability to work well
with the given maven definitions.  I use IntelliJ IDEA for debugging,
which works perfectly.

Regards,
Milan




  parent reply	other threads:[~2022-06-13 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 13:43 Editing Java (with LSP) Alessandro Bertulli
2022-06-13 15:48 ` Filipp Gunbin
2022-06-13 21:53   ` Alessandro Bertulli
2022-06-14 19:12     ` Filipp Gunbin
2022-06-13 20:32 ` Milan Zamazal [this message]
2022-06-16  3:29 ` Pankaj Jangid
2022-06-16 13:34   ` Alessandro Bertulli
2022-06-17  3:27     ` Pankaj Jangid
  -- strict thread matches above, loose matches on Subject: below --
2022-06-13 21:35 Alessandro Bertulli
2022-06-14 19:13 ` Milan Zamazal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkuw5mp4.fsf@zamazal.org \
    --to=pdm@zamazal.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).