dependencies {
- testImplementation("io.github.bonigarcia:webdrivermanager:5.9.1")
+ testImplementation("io.github.bonigarcia:webdrivermanager:5.9.2")
}<dependency>
<groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
- <version>5.9.1</version>
+ <version>5.9.2</version>
<scope>test</scope>
</dependency>dependencies {
- testImplementation("io.github.bonigarcia:webdrivermanager:5.9.1")
+ testImplementation("io.github.bonigarcia:webdrivermanager:5.9.2")
}Using the WebDriverManager fat-JAR (i.e., WebDriverManager with all its dependencies in a single executable JAR file). This JAR file is generated from the source using the Maven command mvn compile assembly:single, and it is released on GitHub with every new version of WebDriverManager. You can download the latest of this fat-JAR from here. Once you get this file, you need to use the following command in the shell (where <args> are the accepted arguments, explained below):
Using the WebDriverManager fat-JAR (i.e., WebDriverManager with all its dependencies in a single executable JAR file). This JAR file is generated from the source using the Maven command mvn compile assembly:single, and it is released on GitHub with every new version of WebDriverManager. You can download the latest of this fat-JAR from here. Once you get this file, you need to use the following command in the shell (where <args> are the accepted arguments, explained below):
java -jar webdrivermanager-5.9.1-fat.jar <args>java -jar webdrivermanager-5.9.2-fat.jar <args>docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.9.1docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.9.2java -jar webdrivermanager-5.9.1-fat.jar resolveDriverFor chromejava -jar webdrivermanager-5.9.2-fat.jar resolveDriverFor chromedocker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.9.1docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.9.2java -jar webdrivermanager-5.9.1-fat.jar runInDocker chromejava -jar webdrivermanager-5.9.2-fat.jar runInDocker chromedocker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.9.1docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.9.2java -jar webdrivermanager-5.9.1-fat.jar serverjava -jar webdrivermanager-5.9.2-fat.jar serverdocker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.9.1docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.9.2To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager fat-JAR using the JVM flag -javaagent:/path/to/webdrivermanager-5.9.1-fat.jar. Alternatively, it can be done using Maven (see a complete project example here).
To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager fat-JAR using the JVM flag -javaagent:/path/to/webdrivermanager-5.9.2-fat.jar. Alternatively, it can be done using Maven (see a complete project example here).
boni@ubuntu:~$ java -jar webdrivermanager-5.9.1-fat.jar resolveDriverFor chrome
+boni@ubuntu:~$ java -jar webdrivermanager-5.9.2-fat.jar resolveDriverFor chrome
[INFO] Using WebDriverManager to resolve chrome
[DEBUG] Detecting chrome version using online commands.properties
[DEBUG] Running command on the shell: [google-chrome, --version]
@@ -2515,7 +2515,7 @@
-docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.9.1
+docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.9.2