Create OOPHM debugger so Eclipse can debug Java directly
This piece is sooo close. Basically, with an OOPHM debugger (written in gwt-node itself), gwt-node can debug directly in Eclipse (mostly) without any extra support. It will also be able to use JUnit (mostly) without any extra support. I may have to make a new set of tools proxying GWTShell and GWTTestCase (and GWTTestSuite) to make this easier for the user.
This is mostly implemented already.
First of all, there is a proxy implemented so you can see all the OOPHM messages back and forth when using regular GWT debugging of a web app.
Second, the source for the debugger is mostly written already and works except for Java/JS invocation. GWT expects these calls to be blocking which node.js doesn't currently support. Sometimes a JS invoke may invoke Java itself which may turn around and invoke JS again. I tried solving this with fibers to no avail.