You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2015/08/25 00:44:45 UTC
[jira] [Resolved] (NUTCH-1948) Make the Selenium remote web driver
specification, configuration and selection available via a Factory-type
mechanism
[ https://issues.apache.org/jira/browse/NUTCH-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney resolved NUTCH-1948.
-----------------------------------------
Resolution: Fixed
resolved in NUTCH-2021
[~momer] I agree about the content being configurable, lets get this done on another ticket.
> Make the Selenium remote web driver specification, configuration and selection available via a Factory-type mechanism
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: NUTCH-1948
> URL: https://issues.apache.org/jira/browse/NUTCH-1948
> Project: Nutch
> Issue Type: Improvement
> Components: plugin, protocol
> Affects Versions: 1.10
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Fix For: 1.11
>
>
> Right now we only use the FirefoxDriver, however we could also use the following
> * ChromeDriver <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/chrome/ChromeDriver.html>,
> * FirefoxDriver <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/firefox/FirefoxDriver.html>,
> * InternetExplorerDriver <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/ie/InternetExplorerDriver.html>, and
> * SafariDriver <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/safari/SafariDriver.html>
> They could be available via a Factory-type mechanism which would allow us to define the driver within nutch-site.xml even.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)