bug#11254: 24.0.94; cannot find compilation-error locations for Java

[Sam Steingold]

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>