From: Sam Steingold <sds@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 11254@debbugs.gnu.org
Subject: bug#11254: 24.0.94; cannot find compilation-error locations for Java
Date: Mon, 7 Dec 2020 13:17:26 -0500 [thread overview]
Message-ID: <CAFsbZ7Zixm7hi8VaoF8sdgh83AqekM5AeQWeCb-9t0P65aVmyg@mail.gmail.com> (raw)
In-Reply-To: <877dptcytl.fsf@gnus.org>
no recollections, sorry.
On Mon, 7 Dec 2020 at 12:26, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Sam Steingold <sds@gnu.org> writes:
>
> > When I work on a maven-managed java project, I add this to
> > java-mode-hook:
> > (set (make-local-variable 'compile-command)
> > (concat "cd " (locate-dominating-file buffer-file-name "pom.xml") " && mvn compile test package"))
> > i.e., M-x compile RET runs maven in a directory far above the location
> > of the current file.
> > The errors in the compilation buffer look like this:
> >
> > java.io.FileNotFoundException: null (No such file or directory)
> > at java.io.FileInputStream.open(Native Method)
> > at java.io.FileInputStream.<init>(FileInputStream.java:137)
>
> [...]
>
> > where every single line in clickable in the most useless way possible:
> > it asks _me_ for a directory where the file in (file.java:lineno) is located.
>
> (This bug report unfortunately got no response at the time.)
>
> I seem to recall there being fixes in this area (Java error parsing)
> over the years -- are you still seeing this problem in recent versions
> of Emacs?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net>
<http://steingoldpsychology.com>
next prev parent reply other threads:[~2020-12-07 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 15:22 bug#11254: 24.0.94; cannot find compilation-error locations for Java Sam Steingold
2020-12-07 17:26 ` Lars Ingebrigtsen
2020-12-07 18:17 ` Sam Steingold [this message]
2020-12-08 13:52 ` Lars Ingebrigtsen
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=CAFsbZ7Zixm7hi8VaoF8sdgh83AqekM5AeQWeCb-9t0P65aVmyg@mail.gmail.com \
--to=sds@gnu.org \
--cc=11254@debbugs.gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).