Details
-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: web-3.0
-
Component/s: Web Selenium
-
Labels:None
-
Number of attachments :
Description
As Selenium 2 is drop-in backward compatible with Selenium 1, having the default dependency on the latest release of Selenium 2 is useful as it can help gradual migration from Selenium to WebDriver.
Users not wanting Selenium 2 in the classpath when using jbehave-web-selenium can simply exclude the dependency
<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium</artifactId> </dependency>
and replace with the Selenium 1 dependency.
Activity
Mauro Talevi
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Mauro Talevi
made changes -
Description |
As Selenium 2 is drop-in backward compatible with Selenium 1, having the default dependency on the latest release of Selenium 2 is useful as it can help gradual migration from Selenium to WebDriver.
Users not wanting Selenium 2 in the classpath when using jbehave-web-selenium can simply exclude the dependency {code:xml} <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium</artifactId> </dependency> {code:xml} and replace with the Selenium 1 dependency. |
As Selenium 2 is drop-in backward compatible with Selenium 1, having the default dependency on the latest release of Selenium 2 is useful as it can help gradual migration from Selenium to WebDriver.
Users not wanting Selenium 2 in the classpath when using jbehave-web-selenium can simply exclude the dependency {code:XML} <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium</artifactId> </dependency> {code} and replace with the Selenium 1 dependency. |