#Use this file to set/override Jasmine configuration options
#This file is loaded *after* jasmine.yml is interpreted.
Jasmine.configure do |config|
  config.prevent_phantom_js_auto_install = true
end

#Use this file to set/override Jasmine configuration options
#You can remove it if you don't need it.
#This file is loaded *after* jasmine.yml is interpreted.
#
#Example: using a different boot file.
#Jasmine.configure do |config|
#   config.boot_dir = '/absolute/path/to/boot_dir'
#   config.boot_files = lambda { ['/absolute/path/to/boot_dir/file.js'] }
#end
#

Allow PhantomJS to be auto-installed again
Allow PhantomJS to be auto-installed again

The [phantomjs gem] can automatically install PhantomJS if it isn't already available on the system.

This functionality was disabled in commit b938bff6f76bc23232b523e0d2a688d34b9d6e22. This was done for security reasons – because at the time, the gem would auto-install from an insecure `http://` URL without performing any file integrity checks.

At that point in time, the Jenkins CI server must have had PhantomJS installed so these tests could run. However this no longer seems to be the case, as builds now fail because they're unable to find the `phantomjs` command.

The security hole was implicitly fixed in colszowka/phantomjs-gem@b41fc6feedd78cf05372c62ca55cf341ec0dc208 when the `http://` URLs were changed to `https://` – which still remains the case in the [current release].

It's therefore safe to re-enable automatic installation, which is now required due to PhantomJS no longer being pre-installed on our Jenkins CI servers.

[phantomjs gem]: https://github.com/colszowka/phantomjs-gem
[current release]: https://github.com/colszowka/phantomjs-gem/blob/38a722deeb7989e2de093fd628139266386492c1/lib/phantomjs/platform.rb#L133
