Include clear cache line in doc about chromedriver 115+

bonigarcia · Aug 22, 2023 · c4ce504 · c4ce504
1 parent 5ac2b89
commit c4ce504
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 2 deletions.
diff --git a/docs/index.html b/docs/index.html
@@ -3030,7 +3030,12 @@ <h4 id="support-for-chromedriver-115" class="discrete">Support for chromedriver
 </div>
 </div>
 <div class="paragraph">
-<p>WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the <strong>latest version</strong> (5.4.1 currently).</p>
+<p>WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the <strong>latest version</strong> (5.4.1 currently). Also, to ensure that the wrong version has not been cached in the <strong>resolution cache</strong>, you can refresh completely the cache folder (at least once) as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="CodeRay highlight"><code data-lang="java">WebDriverManager.chromedriver().clearDriverCache().setup();</code></pre>
+</div>
 </div>
 <div class="paragraph">
 <p>Notice that as of WebDriverManager 5.4, <strong>Java 11</strong> is required. This requirement is mandatory since WebDriverManager is connected to Selenium, and the Selenium team announced that <a href="https://www.selenium.dev/blog/2023/java-8-support/">as of September 2023, the minimum Java version will be Java 11</a>.</p>

diff --git a/docs/webdrivermanager.pdf b/docs/webdrivermanager.pdf
diff --git a/src/doc/asciidoc/index.adoc b/src/doc/asciidoc/index.adoc
@@ -761,7 +761,12 @@ io.github.bonigarcia.wdm.online.HttpClient: Error HTTP 404 executing https://chr
 org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: session not created: This version of ChromeDriver only supports Chrome version 114
 ----
 
-WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the **latest version** ({project-version} currently).
+WebDriverManager 5.4+ implements the support for the CfT endpoints. Therefore, the solution to this problem is to bump WebDriverManager to the **latest version** ({project-version} 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:
+
+[source,java]
+----
+WebDriverManager.chromedriver().clearDriverCache().setup();
+----
 
 Notice that as of WebDriverManager 5.4, **Java 11** is required. This requirement is mandatory since WebDriverManager is connected to Selenium, and the Selenium team announced that https://www.selenium.dev/blog/2023/java-8-support/[as of September 2023, the minimum Java version will be Java 11].