From 16545fbd7f71d351ba9bf2dbc37ac5a8dea5626b Mon Sep 17 00:00:00 2001 From: Boni Garcia Date: Thu, 25 Jul 2024 17:25:00 +0200 Subject: [PATCH] Update doc for release 5.9.2 --- CHANGELOG.md | 6 ++++++ docs/index.html | 36 ++++++++++++++++++------------------ docs/webdrivermanager.pdf | Bin 1710670 -> 1710670 bytes 3 files changed, 24 insertions(+), 18 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d4442fee5..2f92c7bf5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # Changelog +## [5.9.2] - 2024-07-25 + +### Fixed +- HTTP 404 when downloading microsoft edgedriver in macOS or Linux (#1320) + + ## [5.9.1] - 2024-06-24 ### Removed diff --git a/docs/index.html b/docs/index.html index 02dd8d043..83d805c27 100644 --- a/docs/index.html +++ b/docs/index.html @@ -775,7 +775,7 @@

WebDriverManager

Boni García
-Version 5.9.1 +Version 5.9.2
Table of Contents
@@ -1002,7 +1002,7 @@

2. Setup

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

2. Setup

dependencies {
-    testImplementation("io.github.bonigarcia:webdrivermanager:5.9.1")
+    testImplementation("io.github.bonigarcia:webdrivermanager:5.9.2")
 }
@@ -2056,10 +2056,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.9.1-fat.jar <args>
    +
    java -jar webdrivermanager-5.9.2-fat.jar <args>
    2. @@ -2075,7 +2075,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.9.1
    +
    docker run --rm -e ARGS="<args>" bonigarcia/webdrivermanager:5.9.2
    @@ -2113,7 +2113,7 @@

    Option 1: Driver Resolver

    -
    java -jar webdrivermanager-5.9.1-fat.jar resolveDriverFor chrome
    +
    java -jar webdrivermanager-5.9.2-fat.jar resolveDriverFor chrome
    @@ -2137,7 +2137,7 @@

    Option 1: Driver Resolver

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

    Option 2: Browsers in Docker

    @@ -2153,7 +2153,7 @@

    Option 2: Browsers in Dock

    -
    java -jar webdrivermanager-5.9.1-fat.jar runInDocker chrome
    +
    java -jar webdrivermanager-5.9.2-fat.jar runInDocker chrome
    @@ -2177,7 +2177,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.9.1
    +
    docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome" bonigarcia/webdrivermanager:5.9.2
    @@ -2205,7 +2205,7 @@

    Option 3: Server

    -
    java -jar webdrivermanager-5.9.1-fat.jar server
    +
    java -jar webdrivermanager-5.9.2-fat.jar server
    @@ -2229,7 +2229,7 @@

    Option 3: Server

    -
    docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.9.1
    +
    docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.9.2
    @@ -2346,7 +2346,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.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).

    @@ -2390,7 +2390,7 @@

    4.5. Selenium

    -
    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
    
 
    
 
    
 
    
@@ -3068,7 +3068,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.9.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.9.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:
    
 
    
 
    
 
    
@@ -3260,8 +3260,8 @@ 
    12. About
    
 
    
 
 
diff --git a/docs/webdrivermanager.pdf b/docs/webdrivermanager.pdf
index a4ebccc19c7212b2046630db9003ede884c5f1f5..568c45a35278f173f72027f31fd018c0886d50ce 100644
GIT binary patch
delta 356
zcmX@NCF9(dj197koaRQRhUP|w#ul5^7*DbC8yO`V85kQGn;NAU8yK56|7Y9&pN+Bk
z?c^kTt?2>Z8Ev+|_`>KU2Id}k&Z^yB&&>qH%s|Wn#H>Kf2E^<@%mKulK+FZi+(66&
z#JoVv2gLk9EU>+vThO(F(P;b8X2ED-kdc!c*c7*CPZyjn#Aq}MtQ(%Sy`m|!v&M1jcm=!=5A0wB3*UA!#QAH=Y#Z?}CU
zxQG`bFTDNpd%@{Qdhh)dG`I=0g#WUTpETUg=|DSGCU4lxx_#a|p&(13Jkaupmng=z
i&l3~@Vo@L#+dfZFoNEW8QTxi1;y^61edS5Xr2zoCw|sK|

delta 359
zcmX@NCF9(dj197koMuKQhUNxFMy8w97*DbC8yY1W85kQGn;4}S8yK54|7Y9&pN+Bk
z?Q}tF37zQ)9~iB+zxcxFBnIJcc+H~OUeC=0#LPg<0>rF9%m&2lK+FNeoIuP4#N0s4
z1H`;Q%m>8$KrFDmo?Fnhg3)mM(PqJDVUU^L+q0(&P8VV{oF4a1NDL?=wMuXXi2G4p
zICFYH2(SD0