You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2019. It is now read-only.
@smurf667, not sure I understand. The bug you referenced is still open and the release you are linking to is not a phantomjs release. That is phantomjs-node which is an npm module that provides similar functionality that the phantomjs-maven-plugin provides but in a NodeJS environment. So, I'm not sure what that has to do with this plugin. As far as I can see the latest version of PhantomJS is still 2.1.1 which is already supported by the plugin: http://repo1.maven.org/maven2/com/github/klieber/phantomjs/2.1.1/
@smurf667https://github.com/smurf667, not sure I understand. The bug
you referenced is still open and the release you are linking to is not a
phantomjs release. That is phantomjs-node which is an npm module that
provides similar functionality that the phantomjs-maven-plugin provides
but in a NodeJS environment. So, I'm not sure what that has to do with this
plugin. As far as I can see the latest version of PhantomJS is still 2.1.1
which is already supported by the plugin: http://repo1.maven.org/maven2/
com/github/klieber/phantomjs/2.1.1/
Hello Kyle,
it seems a bug troubling many people has finally been adressed: ariya/phantomjs#12750
The fix should be contained in the release 2.1.13
It would be highly appreciated if the Maven plugin could use version 2.1.13 on Linux.
The text was updated successfully, but these errors were encountered: