Reputation: 11356
So for your first NodeJS
project, you install the V8 debugger for Eclipse from ChromeDevTools.
And whenever you have a new NodeJS
project in Eclipse, what you basically do is duplicate your Debug Configuration
and make two changes:
Source Mapper
that connects the project to the local directorySource Mapper
that connects the project to the local/remote hostThis works, no problem.
But the list of Debug Configurations
builds and builds. You'll have to click the debug-dropdown and choose from the list of many debug configurations the one that was meant for your current project.
Debug Configuration
that automatically changes the Source Mappers
based on the current project? Or; Because I always have to click the Debug As...
drop-down and choose the proper configuration.
If I just click the Debug As...
button (the little green bug), I always get this:
Even if I've just debugged.
Upvotes: 1
Views: 993
Reputation: 63872
For the second question about key shortcut, check linked Q to Eclipse - How to assign key shourtcut command to Launch type (Run As type)
Or maybe you want to use Eclipse Runner http://marketplace.eclipse.org/content/eclipse-runner
Upvotes: 0
Reputation: 63872
Try nodeclipse http://www.nodeclipse.org/ that goes with many ChromeDevTools bugs fixed.
Remote debugging is not possible with Nodeclispe, so install it in other Eclispe instance or get Enide Studio http://sf.net/p/nodeclipse
And if it stil won't be enough, I am glad to share what I know to help you with changing ChromeDevTools in the way you want https://github.com/nodeclipse/nodeclipse-1/.
Upvotes: 1