Kdevelop java language support plugin

--000000000000f62c390647cb4afb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

Thanks for your reply. I probably should clarify what state my work on this
project is in. I have updated practically all of the c++ code in the
project and, as far as I can tell, it is almost in a completely working
state. I am mostly having issues with the grammar file, as I have no
previous experience with how  things like it are written. Theoretically, it
should be fully functional for java versions up to 1.5, but I have yet to
test that. At this point, the grammar file is all that needs to be updated.
There are some issues with formatting and a lot of things which could be
optimized, though I would only want to work on them after the parser is
functional.

Thanks again,
Caroline

On Tue, Jan 6, 2026 at 6:25=E2=80=AFAM Sven Brauch <mail-ITmcY+a7/[email protected]> wro=
te:

> Hi,
>
> On 1/6/26 08:10, Milian Wolff wrote:
> > Generally, a much better path forward would be
> > to integrate the language agnostic LSP into kdevelop, and then get java
> > support through there somehow.
>
> FWIW, Kate's LSP plugin is available in KDevelop, at least
> rudimentarily, and it does already integrate the Java LSP. Maybe try
> that out first.
>
> Getting kdev-java up to speed will definitely be a huge effort which I'm
> honestly not sure is worth it at this point.
>
> Greetings!
> Sven
>
>

--000000000000f62c390647cb4afb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>Thanks for your reply. I probabl=
y should clarify what state my work on this project is in. I have updated p=
ractically all of the c++ code in the project and, as far as I can tell, it=
 is almost in a completely=C2=A0working state. I am mostly having issues wi=
th the grammar file, as I have no previous experience with how=C2=A0 things=
 like it are written. Theoretically, it should be fully functional for java=
 versions up to 1.5, but I have yet to test that. At this point, the gramma=
r=C2=A0file is all that needs to be updated. There are some issues with for=
matting and a lot of things which could be optimized, though I would only w=
ant to work on them after the parser is functional.</div><div><br></div><di=
v>Thanks again,</div><div>Caroline</div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 6, 2026 at 6:25=E2=80=
=AFAM Sven Brauch &lt;<a href=3D"mailto:mail-ITmcY+a7/[email protected]" target=3D"_blan=
k">mail-ITmcY+a7/[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">Hi,<br>
<br>
On 1/6/26 08:10, Milian Wolff wrote:<br>
&gt; Generally, a much better path forward would be<br>
&gt; to integrate the language agnostic LSP into kdevelop, and then get jav=
a<br>
&gt; support through there somehow. <br>
<br>
FWIW, Kate&#39;s LSP plugin is available in KDevelop, at least <br>
rudimentarily, and it does already integrate the Java LSP. Maybe try <br>
that out first.<br>
<br>
Getting kdev-java up to speed will definitely be a huge effort which I&#39;=
m <br>
honestly not sure is worth it at this point.<br>
<br>
Greetings!<br>
Sven<br>
<br>
</blockquote></div>

--000000000000f62c390647cb4afb--