Eclipse Community Forums: Java Development Tools (JDT)

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Debugging jdt.core

Show: Today's Messages :: Show Polls :: Message Navigator

Debugging jdt.core [message #1755854]

Wed, 08 March 2017 16:01

Ivan Kulezic

Messages: 7
Registered: February 2017

Junior Member

I'm working on adapting jdt.core for a language similar to Java and I successfully added changes I wanted and compiled jdt.core (skipped test stage). After that I imported newly created plug-in into Eclipse (Neon) but it doesn't work the way I wanted. Is there a way to debug it?

What IDE to use for developing jdt.core? I tried using both Eclipse and NetBeans but the maven project can't be imported properly therefore I can't debug it.

Report message to a moderator

Re: Debugging jdt.core [message #1755884 is a reply to message #1755854]

Wed, 08 March 2017 22:33

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

Ivan Kulezic wrote on Wed, 08 March 2017 17:01

I'm working on adapting jdt.core for a language similar to Java and I successfully added changes I wanted and compiled jdt.core (skipped test stage). After that I imported newly created plug-in into Eclipse (Neon) but it doesn't work the way I wanted. Is there a way to debug it?

What IDE to use for developing jdt.core? I tried using both Eclipse and NetBeans but the maven project can't be imported properly therefore I can't debug it.

"NetBeans"? That was a good one ROTFL Laughing

(historical note: JDT is an excellent example of "dog-fooding": for as long as Eclipse and JDT are open source, Eclipse has been used for developing Eclipse and JDT in particular has been used to develop JDT).

Seriously: the most promising way for hacking on JDT code these days should be the Oomph installer, which comes with a predefined setup for JDT. Have you seen that? (Note to self: last time there were still some hick-ups which I meant to investigate).

Secondly, while you'll find pom files all over the place that's not what we use for development, those are mainly for production builds. So instead of importing "as maven project" you should preferrably let Oomph take care of everything, or if that doesn't work for you (it should): directly import the existing projects from git: all projects have their .project and .classpath in git so no need to let some wizard generate project configurations on the fly. It's all there in git.

Report message to a moderator