anchor.diff:  
   * Fat-JAR:
   
  +[source,shell,subs="attributes+"]
  +----
  +java -jar webdrivermanager-{project-version}-fat.jar resolveDriverFor chrome
  +----
  +
  +* Source code:
  +
   [source,shell]
   ----
  -java -jar webdrivermanager-5.0.0-fat.jar resolveDriverFor chrome
  -----
  -
  -* Source code:
  -
  -[source,shell]
  -----
   mvn exec:java -Dexec.args="resolveDriverFor chrome"
   ----
   
   * Docker container:
   
  -[source,shell]
  -----
  -docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.0.0
  +[source,shell,subs="attributes+"]
  +----
  +docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:{project-version}
   ----
   
   [discrete]
  
positive.code: 
  * Fat-JAR:
  
  [source,shell]
  ----
  java -jar webdrivermanager-5.0.0-fat.jar server
  ----
  
  * Source code:
  
  [source,shell]
  ----
  mvn exec:java -Dexec.args="server"
  ----
  
  * Docker container:
  
  [source,shell]
  ----
  docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.0.0
  ----
  
  === WebDriverManager Server
  
negative.code: 
  For example, this https://github.com/bonigarcia/webdrivermanager/blob/master/src/test/java/io/github/bonigarcia/wdm/test/create/ChromeRemoteTest.java[test] shows how to start a Selenium Grid in standalone mode, resolving the driver with WebDriverManager and registering a Chrome browser in the Selenium Server. In addition, if we start Selenium Grid from the shell, we can complement it with WebDriverManager CLI to resolve the required drivers, as follows:
  
  [source,shell,subs="attributes+"]
  ----
  boni@ubuntu:~$ java -jar webdrivermanager-{project-version}-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]
  