Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Status and future outlook of the JSDT debugger

Hi Ivan,

I'm very glad that you post this question because in my case I need to debug TypeScript (in other mean debugging with source map).

So I have created a patch for JSDT Chrome debugger at and sourcemap code is based on your sdbg work. See my comment at

My patch is not perfect but I hope JSDT Team will accept it and hope guys like you will improve it.

Regard's Angelo

2017-01-21 10:06 GMT+01:00 Ivan Markov <ivan.markov@xxxxxxxxx>:
Dear all,

Being the maintainer of, the recent (2015-2016) rebirth of the JSDT tooling is of course something I'm interested it.
(... and unfortunately something I've slept through).

Regarding the JSDT debugging story, as far as I understand there are two codebases in use:
1) The original JSDT Debug plugins, which support only Rhino
2) A fork of the old Chromedevtools-Java tooling from Google (last when I looked at it - still in the Google Code times, it was a completely independent set of Eclipse plugins, is this still the case?)

The following question to follow (obviously):
Have you considered using the SDBG codebase, and if not, why not? Technical or legal issues?


wtp-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top