I just tried running the functional tests and something weird is going on. The mssoapinterop.org site seems to be down, which is timing out the WSDL2Java stuff. For one thing, we're apparently bubbling up Exceptions about the connect timeout instead of printing the nice timeout message (only some of the time though!), and for another, the build just stops after the InteropC.wsdl timeout. No "BUILD FAILED" message, nothing - just stops.
Russell, does this have to do with the revamped WSDL2Java (does it deal with timeouts differently?)? Anyone else seeing this behaviour? --Glen
