guard-jasmine uses wrong mechanism to communicate port to jasmine

[kdeberk]

I'm using the following two gems:

• guard-jasmine-2.1.0
• jasmine-2.6.0

When I execute bundle exec guard-jasmine spec, it tries to start jasmine on a free port. It communicates the chosen port with the environment variable JASMINE_PORT, but jasmine has not been using that variable since 1.3.2.

jasmine uses port 8888 and url http://localhost by default so to get the following command to work, you need to set the port and url to the default jasmine values.

> bundle exec guard-jasmine spec
Guard::Jasmine starts Jasmine Gem test server on port 43843.
Timeout while waiting for the server to startup
Most likely there is a configuration error that's preventing the server from starting
You may need to increase the `:server_timeout` option.
The commandline that was used to start the server was:
ruby -S rake jasmine JASMINE_PORT=43843
You should attempt to run that and see if any errors occur
Waiting for Jasmine test runner at http://localhost:43843/jasmine
Jasmine test runner isn't available: Connection refused - connect(2) for "localhost" port 43843
Guard::Jasmine stops server.


> bundle exec guard-jasmine spec --port 8888 --url http://localhost:8888/
Guard::Jasmine starts Jasmine Gem test server on port 8888.
Waiting for Jasmine test runner at http://localhost:8888/
Run all Jasmine suites
....