all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Steinar Bang <sb@dod.no>
To: help-gnu-emacs@gnu.org
Subject: Re: Looking for active JDEE mailing lists or forums
Date: Sun, 12 May 2019 16:58:03 +0200	[thread overview]
Message-ID: <865zqfoh38.fsf@dod.no> (raw)
In-Reply-To: <CAM-tV--WJ+BvhghF32XOg5mWf1VXwrf7ApzF=4muLtyoxz_kUA@mail.gmail.com> (Noam Postavsky's message of "Tue, 2 Apr 2019 08:16:14 -0400")

>>>>> Noam Postavsky <npostavs@gmail.com>:

> On Sun, 31 Mar 2019 at 12:52, Steinar Bang <sb@dod.no> wrote:
>>> According to https://github.com/jdee-emacs/jdee/issues/162#issuecomment-442050766

>>>     Everything now goes through GitHub.

>> Yes, I saw that.  But what does it mean?

>> Do they use the issue tracker as the support forum/discussion forum?

> Yes, that's how I understood it.

FWIW I eventually gave up on JDEE and am now back on the regular
java-mode.  

JDEE didn't work right out of the box (I got heaps of error messages,
and huge emacs desktop restore CPU usage (from the mvn builds), and at
the end the .java files were cluttered with flycheck errors, with no way
to navigate to the errors, and no clear indication what the errors were)
and the documentation is seriously outdated, and there is no forum, and
all google searches for JDEE problems give outdated answers.

There is activity on the github repo, so there are people working on
JDEE... but actually using it turned out to be more work than it was
worth.

Oh well!



      reply	other threads:[~2019-05-12 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31 15:52 Looking for active JDEE mailing lists or forums Steinar Bang
2019-03-31 16:00 ` Noam Postavsky
2019-03-31 16:52   ` Steinar Bang
2019-04-02 12:16     ` Noam Postavsky
2019-05-12 14:58       ` Steinar Bang [this message]

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

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

  git send-email \
    --in-reply-to=865zqfoh38.fsf@dod.no \
    --to=sb@dod.no \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.