Update README.md

Author: etiennestuder

README.md

@@ -33,7 +33,7 @@ The following functionality is provided by the rocker plugin:
 The following Gradle configuration changes are contributed by the rocker plugin:
 
  * Add the `com.fizzed:rocker-compiler` dependency needed to execute the Rocker template engine to the new `rockerCompiler` configuration  
- * Add the `com.fizzed:rocker-runtime` dependency to the name-matching `compile` configuration to successfully compile the Java sources generated from the Rocker templates
+ * Add the `com.fizzed:rocker-runtime` dependency to the name-matching `implementation` configuration to successfully compile the Java sources generated from the Rocker templates
  * Use the customizable Rocker version across all `com.fizzed:rocker-*` dependencies
 
 The following Gradle features are supported by the rocker plugin:
@@ -96,7 +96,7 @@ rocker {
   }
 }
 
-rockerVersion = '0.20.0'  // optional
+rockerVersion = '1.2.2'  // optional
 ```
 
 The rocker _main_ configuration declares that the Rocker templates are in _src/rocker_ and the generated Java sources need to end up in _src/generated/rocker_. It further 
@@ -106,7 +106,7 @@ of the configuration is `main`, the generated sources are added to the `main` so
 Given the configuration above, you can invoke the Rocker template engine by issuing `./gradlew compileRocker`. You can also directly call `./gradlew compileJava` which first
 generates the Java sources from the Rocker templates, and then compiles these Java sources as part of compiling all sources in the _main_ source set. 
 
-Since we declared to use version _0.20.0_ of the Rocker template engine, all Rocker dependencies of all Gradle configurations will be of that given version. 
+Since we declared to use version _1.2.2_ of the Rocker template engine, all Rocker dependencies of all Gradle configurations will be of that given version. 
 
 > I suggest you use the [Continuous build](https://docs.gradle.org/current/userguide/continuous_build.html) feature of Gradle instead of using the Rocker hot reload feature.
 > Declare `optimize = true` in the rocker configuration of your Gradle build, and then run your build with the `-t` command line option. In addition, deactivating the hot