The configuration of the jar package is in the project-level Pom.xml file
When we do selenium automated testing, we often encounter the situation: the browser quietly upgraded. Immediately thereafter all test cases fail.
After checking the log found that the original is an upgraded browser, we use the original selenium has been unable to operate.
So, had to go to selenium official website re-download ...
This process is too cumbersome, and using Maven's RAnge dependency mechanism can save this step:
<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId> Selenium-java</artifactid> <version>[2.40.0,) </version> </dependency>
Note that the [2.40.0,] in version shows the latest version of 2.40.0. When I write version like this, the jar packages in my selenium framework are automatically upgraded, and now they themselves become 2.41.0 version.
MAVEN Auto Update jar Package