Eclipse Community Forums: Java Development Tools (JDT) » directing debugger to non-java source editor

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » directing debugger to non-java source editor

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

directing debugger to non-java source editor [message #152373]

Mon, 05 April 2004 15:20

Dan Jacobs

Messages: 13
Registered: July 2009

Junior Member

Hi all,

We're developing a pluging for JPlates, which is a template-processing
extension of Java that compiles into Java. See www.jplates.com for more.

We are performing minor surgery on the class files after Eclipse compiles
the generated Java, modifying the SourceFile attribute to point back to the
JPlates source, and the line-number-table to correctly resolve back to the
right line-numbers of the JPlates sources.

I would have thought that the class-file surgery would be enough for the
Eclipse debugger to want to open the appropriate JPlates sources in the
JPlates editor, but instead it opens the [rather less aesthetically
pleasing] generated Java sources in the Java editor.

I have been able to set breakpoints in the JPlates editor, but there must
be some additional magic trick I need to get the debugger to believe that
it should work with the JPlates sources and JPlates editor.

Does anyone know what that magic might be?

Thanks in advance,
Dan Jacobs
President, JPlates Inc.

Report message to a moderator

Re: directing debugger to non-java source editor [message #152586 is a reply to message #152373]

Tue, 06 April 2004 02:11

Dan Jacobs

Messages: 13
Registered: July 2009

Junior Member

OK, I know I could earn an odd reputation for responding to my own posts
all the time, but after *much* more searching, I came across a nearly
unrelated reference to ISourceLocator, which I will pursue.

So now my question is: Is there a better approach to becoming a competent
Eclipse developer than stumbling through the API hoping to find something
relevant?

I've got a couple of books (Shavor et al is excellent), but there's a lot
more involved in developing a really sophisticated plugin (such as for
supporting a language that extends Java) that I don't ever expect to see in
a book for the average plugin developer.

Any pointers would be appreciated - but expect more postings (and replies) too.

Cheers,
-- Dan

Dan Jacobs wrote:

> Hi all,
>
> We're developing a pluging for JPlates, which is a template-processing
> extension of Java that compiles into Java. See www.jplates.com for more.
>
> We are performing minor surgery on the class files after Eclipse
> compiles the generated Java, modifying the SourceFile attribute to point
> back to the JPlates source, and the line-number-table to correctly
> resolve back to the right line-numbers of the JPlates sources.
>
> I would have thought that the class-file surgery would be enough for the
> Eclipse debugger to want to open the appropriate JPlates sources in the
> JPlates editor, but instead it opens the [rather less aesthetically
> pleasing] generated Java sources in the Java editor.
>
> I have been able to set breakpoints in the JPlates editor, but there
> must be some additional magic trick I need to get the debugger to
> believe that it should work with the JPlates sources and JPlates editor.
>
> Does anyone know what that magic might be?
>
> Thanks in advance,
> Dan Jacobs
> President, JPlates Inc.
>

Report message to a moderator

Previous Topic:	problem with Marker persistence in 3.0 M7
Next Topic:	M8: Usability with multiple editors

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Sep 01 07:45:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter