@paulvi - you've reported a long time ago that Webclispe JS Debugger cannot be installed into Nodeclipse. The reason for that is usage of Chrome Dev Tools Plugins in both solutions and a different approach for setting up breakpoints, launch configs etc.

As far as I can see, core of your tooling is tightly connected to Chrome Dev Tools plugins, which we heavily modify, and the only way to allow your users to install more powerful debugger would be to create an abstraction layer. This is an extended task and I've managed to find resources for it only now.

So, my proposition is that I would work on abstracting your code to allow usage of different debuggers. I don't know yet if this is possible, but if yes, than it will result in a pull request and would require a new release of Nodeclipse. My plan is to create a separate Nodeclipse feature called "Nodeclipse default debugger (optional)" (or something better sounding), which would be installable from your update site and "Webclipse JavaScript Debugger - Nodeclipse support", which would be installable from our update site (or if you would like to, from yours as well). Thus, if user tries to install our debugger, yours would be uninstalled and all the features would work with the new one.

Since the initial release we've improved overall quality of the feature and added following features:

• sourcemap support for both Node.js and Chrome
• JavaScript code hot-sync to Chrome
• connection to externally launched Node.js

Please let me know if you are interested in making such a change and we can start discussion about technical details if you are :)