remoteWebDriverUrl property (allows phantomjs to be used)

This is one way to go to enable phantomjs.  Another would be to support something like "phantoms.home" (config property and/or environment variable) and perhaps a port property - the plugin would then start and stop the phantomjs process. This is simpler (and more generic) and I didn't feel a compelling reason to go the other way.  But whatever you decide is fine.  

We communicated earlier but just to reiterate - to use the phantomjs web driver you would need to have it (version 1.8+) installed somewhere (not necessarily the build machine) and it needs to run via the command line phantomjs --webdriver=PORT.

In my testing performance and compatibility are both drastically improved.

Thanks!