{"action":"closed","issue":{"url":"https://api.github.com/repos/klieber/phantomjs-maven-plugin/issues/25","labels_url":"https://api.github.com/repos/klieber/phantomjs-maven-plugin/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/klieber/phantomjs-maven-plugin/issues/25/comments","events_url":"https://api.github.com/repos/klieber/phantomjs-maven-plugin/issues/25/events","html_url":"https://github.com/klieber/phantomjs-maven-plugin/issues/25","id":47934208,"number":25,"title":"Configurable phantomjs binary filename","user":{"login":"topsy-turvy","id":9586991,"avatar_url":"https://avatars.githubusercontent.com/u/9586991?v=3","gravatar_id":"","url":"https://api.github.com/users/topsy-turvy","html_url":"https://github.com/topsy-turvy","followers_url":"https://api.github.com/users/topsy-turvy/followers","following_url":"https://api.github.com/users/topsy-turvy/following{/other_user}","gists_url":"https://api.github.com/users/topsy-turvy/gists{/gist_id}","starred_url":"https://api.github.com/users/topsy-turvy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/topsy-turvy/subscriptions","organizations_url":"https://api.github.com/users/topsy-turvy/orgs","repos_url":"https://api.github.com/users/topsy-turvy/repos","events_url":"https://api.github.com/users/topsy-turvy/events{/privacy}","received_events_url":"https://api.github.com/users/topsy-turvy/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/klieber/phantomjs-maven-plugin/labels/wontfix","name":"wontfix","color":"ffffff"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2014-11-06T08:19:00Z","updated_at":"2015-04-28T16:49:37Z","closed_at":"2015-04-28T16:49:37Z","body":"It would be nice to be able to specify phantomjs binary path without invoking 'install' goal.\r\n\r\nCurrently jasmine-maven-plugin relies on ${phantomjs.binary} property set by phantomjs-maven-plugin within 'install' goal. While it is okay for CI build, it makes impossible to run jasmine-maven-plugin:test goal separately on developer host. Right now it is possible to specify 'outputDirectory' property but the final path will be OS specific anyway (phantomjs.exe vs phantomjs). I suggest to add 'outputBinaryPath' which will be the final full path of binary including executable filename. I.e.\r\n\r\n`<outputBinaryPath>`target/phantomjs-dir/custom-phantomjs-name`</outputBinaryPath>`\r\n\r\nmeans to extract binary to '${project.dir}/target/phantomjs-dir', rename 'phantomjs' to 'custom-phantomjs-name' and grant it executable rights. This way 'install' goal on developer host can be run only once and will extract binary to predictable path. Then jasmine:test goal can be used with specified 'phantomjs.binary.path' equals to 'outputBinaryPath' value."}}