On Sat, Jan 21, 2017 at 4:06 AM, Ivan Markov <[email protected]> wrote:
> Dear all, > > Being the maintainer of sdbg.github.io, 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? > > No, we have not considered it. At least I have assumed it to be GWT only. > Cheers, > Ivan > > > > > _______________________________________________ > wtp-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/wtp-dev >
_______________________________________________ wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
