dependencies {
- testImplementation("io.github.bonigarcia:webdrivermanager:5.5.3")
+ testImplementation("io.github.bonigarcia:webdrivermanager:5.6.0")
}<dependency>
<groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
- <version>5.5.3</version>
+ <version>5.6.0</version>
<scope>test</scope>
</dependency>dependencies {
- testImplementation("io.github.bonigarcia:webdrivermanager:5.5.3")
+ testImplementation("io.github.bonigarcia:webdrivermanager:5.6.0")
}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.5.3-fat.jar <args>java -jar webdrivermanager-5.6.0-fat.jar <args>docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.5.3docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.6.0java -jar webdrivermanager-5.5.3-fat.jar resolveDriverFor chromejava -jar webdrivermanager-5.6.0-fat.jar resolveDriverFor chromedocker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.5.3docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.6.0java -jar webdrivermanager-5.5.3-fat.jar runInDocker chromejava -jar webdrivermanager-5.6.0-fat.jar runInDocker chromedocker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.5.3docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.6.0java -jar webdrivermanager-5.5.3-fat.jar serverjava -jar webdrivermanager-5.6.0-fat.jar serverdocker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.5.3docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.6.0To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager fat-JAR using the JVM flag -javaagent:/path/to/webdrivermanager-5.5.3-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.6.0-fat.jar. Alternatively, it can be done using Maven (see a complete project example here).
boni@ubuntu:~$ java -jar webdrivermanager-5.5.3-fat.jar resolveDriverFor chrome
+boni@ubuntu:~$ java -jar webdrivermanager-5.6.0-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]
@@ -2514,7 +2514,7 @@
-docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.5.3
+docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.6.0
@@ -2739,6 +2739,12 @@ Avoid shutdown hook for drivers objected created with create()
+avoidExternalConnections()
wdm.avoidExternalConnections=true
false
Avoid connections to external urls, useful when downloading webdrivers from an artifact storage in an intranet
+
browserVersionDetection Command(String)
wdm.browserVersion DetectionCommand
"" (automatic discovery using the commands database)
-WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the latest version (5.5.3 currently). Also, to ensure that the wrong version has not been cached in the resolution cache, you can refresh completely the cache folder (at least once) as follows:
+WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the latest version (5.6.0 currently). Also, to ensure that the wrong version has not been cached in the resolution cache, you can refresh completely the cache folder (at least once) as follows: