Folks, A warning - after I chased my tail for a day with a bug that was very hard to pin down.
Turned up running NodeLauncherTestCase in node-launcher-equinox after I had made a change in a completely different module - Assembly.
What I started getting were NoClassDefFound errors for ContributionScanner when trying to load the ContributionContentProcessor from NodeImpl in the startup phase. The worst aspect was that these errors were intermittent - they happened often, but not every time - and trying to use the debugger in Eclipse usually made the code work - but not always.
Eventually, I managed to get the ClassLoader code to stop at the point where it was throwing the exception and discovered to my surprise that the Bundle doing the loading was not node-impl but rather node-impl2. Removing the node-impl2 module from my system solved the problem.
Now, node-impl2 isn't part of the mainline build so you'd expect it not to get used. And in general this is true. However, the class loading under OSGi is different - and if node-impl2 is there in your modules directory, it is fair game for loading under OSGi for some configurations. And for whatever reason, it screws up the classloading.
Yours, Mike
