Before dropping back to offline mode, the new deployer tries to auto-connect to a server running on the local machine. Since this feature was added I have run into a problem where it is connecting to the wrong server. For example, the Geronimo build will just hang during assembly if there is another server running in the background.
There has been talk about splitting the online and offline functions into two tools; if this is done I don't think this will continue to be an issue as the online one could try and connect but the offline one which is used during the build won't.
If we stick with one tool them I think we should add a --offline option that stops the deployer from trying to connect. It seems to me that one tool approach is getting confusing.