Server starts even if port is already in use

[cschuff]

Hi there,

I locally have tomcat running on port 8080. When I fire up a server with gulp-connect it 'successfully' starts on the same port (it's default port 8080) without giving any notice.

Imho the server startup should fail with an adequate error message like: "Port '8080' is already in use!" This is what it does:
"Server started http://localhost:8080"

It would be even better if gulp-connect could automatically pick a free port if the specified port is already in use.

BR
Chris