From f3451eb893e6bfd7dbe9d415b50d6b1cbb069372 Mon Sep 17 00:00:00 2001 From: Boni Garcia Date: Tue, 7 Nov 2023 10:09:52 +0100 Subject: [PATCH] Update doc for version 5.6.2 --- CHANGELOG.md | 6 ++++++ docs/index.html | 36 ++++++++++++++++++------------------ docs/webdrivermanager.pdf | Bin 1722892 -> 1722892 bytes 3 files changed, 24 insertions(+), 18 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6eac5123b..48af68310 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # Changelog +## [5.6.2] - 2023-11-07 + +### Fixed +- Fix logic to find driver version from CfT URL (#1160) + + ## [5.6.1] - 2023-11-02 ### Fixed diff --git a/docs/index.html b/docs/index.html index 1ca3593a2..8f64cf190 100644 --- a/docs/index.html +++ b/docs/index.html @@ -775,7 +775,7 @@

WebDriverManager

Boni García
-Version 5.6.1 +Version 5.6.2
Table of Contents
@@ -1002,7 +1002,7 @@

2. Setup

<dependency>
     <groupId>io.github.bonigarcia</groupId>
     <artifactId>webdrivermanager</artifactId>
-    <version>5.6.1</version>
+    <version>5.6.2</version>
     <scope>test</scope>
 </dependency>
@@ -1013,7 +1013,7 @@

2. Setup

dependencies {
-    testImplementation("io.github.bonigarcia:webdrivermanager:5.6.1")
+    testImplementation("io.github.bonigarcia:webdrivermanager:5.6.2")
 }
@@ -2055,10 +2055,10 @@

  1. -

    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.6.1-fat.jar <args>
    +
    java -jar webdrivermanager-5.6.2-fat.jar <args>
    2. @@ -2074,7 +2074,7 @@

    Using the WebDriverManager Docker container. Each new release of WebDriverManager is pushed to Docker Hub as a container based on OpenJDK plus the WebDriverManager fat-JAR. The default command to run the WebDriverManager Docker container is described below.

    -
    docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.6.1
    +
    docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.6.2
    @@ -2112,7 +2112,7 @@

    Option 1: Driver Resolver

    -
    java -jar webdrivermanager-5.6.1-fat.jar resolveDriverFor chrome
    +
    java -jar webdrivermanager-5.6.2-fat.jar resolveDriverFor chrome
    @@ -2136,7 +2136,7 @@

    Option 1: Driver Resolver

    -
    docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.6.1
    +
    docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.6.2

    Option 2: Browsers in Docker

    @@ -2152,7 +2152,7 @@

    Option 2: Browsers in Dock

    -
    java -jar webdrivermanager-5.6.1-fat.jar runInDocker chrome
    +
    java -jar webdrivermanager-5.6.2-fat.jar runInDocker chrome
    @@ -2176,7 +2176,7 @@

    Option 2: Browsers in Dock

    -
    docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.6.1
    +
    docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.6.2
    @@ -2204,7 +2204,7 @@

    Option 3: Server

    -
    java -jar webdrivermanager-5.6.1-fat.jar server
    +
    java -jar webdrivermanager-5.6.2-fat.jar server
    @@ -2228,7 +2228,7 @@

    Option 3: Server

    -
    docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.6.1
    +
    docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.6.2
    @@ -2345,7 +2345,7 @@

    -

    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.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.6.2-fat.jar. Alternatively, it can be done using Maven (see a complete project example here).

    @@ -2389,7 +2389,7 @@

    4.5. Selenium

    -
    boni@ubuntu:~$ java -jar webdrivermanager-5.6.1-fat.jar resolveDriverFor chrome
+
    boni@ubuntu:~$ java -jar webdrivermanager-5.6.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]
@@ -2514,7 +2514,7 @@ 
    
 
    
 
    
-
    docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.6.1
    
+
    docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" -e WDM_CHROMEVERSION=84 bonigarcia/webdrivermanager:5.6.2
    
 
    
 
    
 
    
@@ -3073,7 +3073,7 @@ 
    
-
    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.1 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.2 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:
    
 
    
 
    
 
    
@@ -3265,8 +3265,8 @@ 
    12. About
    
 
    
 
 
diff --git a/docs/webdrivermanager.pdf b/docs/webdrivermanager.pdf
index c8291374e48083e290bb8a0148e0848f3437e185..234b65e528ea011aeeb71b98978662ace8330519 100644
GIT binary patch
delta 393
zcmeB~lG!sQbAucso4KKZfw{?M6~@b~oJK~;Mh3#5Yt&xP%>=~EK+FQftU$~L#Oy%K0mPg@%mu{UK+FTgyg_C^%h6!brb7H7TVivn;hJH!&|UJ+(;J
zRL@M$XnVjG!5Kn8Z7+`r-r1Xp3`6k-uFxCxYWzAF?Ujnnq&K-*QOJ6r`?b>)XpkR_whbf7yj
zrw3f&)!x3_NchkTBunq-vTC$nmKFhGQ6LuEepy;v^Dd)N``;hpKrFHS?+;1-Kmfj^
BjL`r9

delta 378
zcmeB~lG!sQbAucso3VkViK)S66~@b~oQ6ipMh3P$T+t?X9-%f8jF0M2Ez*k1A
z?eD)ZI*CE}0@A`N)9ZzWS=-yVnShuXh*^Lb#AgFyb|B^eVoo6D0%C3;<^f_}Am#&N
zejpau-o`Ch)Wm4G{b#RWv@pnE@9py!3eFUgFw`$kO-d=sEK4oQP0UM7Pc70l)icvG
z+#aw+aE1_2$ID}acQ`>h{H8DX&BVT4>Y`v07f`(Rw%~jLkhs?Lf_f&F>GeyP)VCMD
z5nRLzloa_TxC&X5FpH4>O`y2*U7-MJoOVtJ+Nm<#;VKjB_A5Vxf-D&grvq)zoE~t6
xS9|+zBjH0YknFpk%c{|SSy}{$MS)ms`(