Update references from 0.4 to 1.0

Author: etiennestuder

README.md

@@ -6,16 +6,16 @@ gradle-rocker-plugin
 # Overview
 
 [Gradle](http://www.gradle.org) plugin that integrates the Rocker template engine. For each named rocker configuration declared
-in the build, the plugin adds a task to generate the Java sources from the specified Rocker templates and includes the 
-generated Java sources in the matching source set, if existing. The code generation tasks participate in incremental builds and 
+in the build, the plugin adds a task to generate the Java sources from the specified Rocker templates and includes the
+generated Java sources in the matching source set, if existing. The code generation tasks participate in incremental builds and
 in task output caching by the [Gradle build cache](https://docs.gradle.org/current/userguide/build_cache.html). Additionally,
-the compile task itself is incremental, meaning it is optimized so that only templates which have changed are regenerated. 
+the compile task itself is incremental, meaning it is optimized so that only templates which have changed are regenerated.
 The plugin can be applied on both Java projects and Android projects.
 
 You can find out more details about the actual Rocker source code generation in the [Rocker documentation](https://github.com/fizzed).
 
 The rocker plugin is hosted at [Bintray's JCenter](https://bintray.com/etienne/gradle-plugins/gradle-rocker-plugin).
- 
+
 ## Build scan
 
 Recent build scan: https://scans.gradle.com/s/nrhggndytzjze
@@ -25,22 +25,22 @@ Find out more about build scans for Gradle and Maven at https://scans.gradle.com
 # Functionality
 
 The following functionality is provided by the rocker plugin:
- 
+
  * Generate Java sources from a given set of Rocker templates
  * Add the generated Java sources to the name-matching source set, if existing
- * Wire task dependencies such that the Java sources are generated before the Java compile task of the name-matching source set compiles them, if existing  
+ * Wire task dependencies such that the Java sources are generated before the Java compile task of the name-matching source set compiles them, if existing
 
 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-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 `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:
- 
- * `RockerCompile` task instances are themselves incremental  
- * `RockerCompile` task instances participate in incremental builds  
- * `RockerCompile` task instances participate in task output caching (if the rocker hot reload feature is disabled) 
+
+ * `RockerCompile` task instances are themselves incremental
+ * `RockerCompile` task instances participate in incremental builds
+ * `RockerCompile` task instances participate in task output caching (if the rocker hot reload feature is disabled)
 
 # Configuration
 
@@ -56,7 +56,7 @@ buildscript {
         jcenter()
     }
     dependencies {
-        classpath 'nu.studer:gradle-rocker-plugin:0.4'
+        classpath 'nu.studer:gradle-rocker-plugin:1.0'
     }
 }
 
@@ -67,20 +67,20 @@ apply plugin: 'nu.studer.rocker'
 
 ```groovy
 plugins {
-  id 'nu.studer.rocker' version '0.4'
+  id 'nu.studer.rocker' version '1.0'
 }
 ```
 
-Please refer to the [Gradle DSL PluginDependenciesSpec](http://www.gradle.org/docs/current/dsl/org.gradle.plugin.use.PluginDependenciesSpec.html) to 
+Please refer to the [Gradle DSL PluginDependenciesSpec](http://www.gradle.org/docs/current/dsl/org.gradle.plugin.use.PluginDependenciesSpec.html) to
 understand the behavior and limitations when using the new syntax to declare plugin dependencies.
 
 ## Define rocker configurations
 
 This is a sample configuration:
- 
+
 ```groovy
 plugins {
-    id 'nu.studer.rocker' version '0.4'
+    id 'nu.studer.rocker' version '1.0'
     id 'java'
 }
 
@@ -99,23 +99,23 @@ rocker {
 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 
-declares via the _optimize_ property that the generated Java sources should be optimized to not contain any code that allows for hot reload via Rocker. Since the name 
+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
+declares via the _optimize_ property that the generated Java sources should be optimized to not contain any code that allows for hot reload via Rocker. Since the name
 of the configuration is `main`, the generated sources are added to the `main` source set contributed by the applied `java` plugin.
 
 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. 
+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 _1.2.2_ 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 
+> 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
 > reload feature of Rocker will enable the rocker tasks for task output caching by the [Gradle build cache](https://docs.gradle.org/current/userguide/build_cache.html).
 
 ## Complete rocker configuration options
 
 For each named configuration, the following options can be configured:
- 
+
   * `optimize` (boolean): if _true_, hot reload support is removed from the generated templates, task output becomes cacheable
   * `extendsClass` (String): the class that all template implementations should extend
   * `extendsModelClass` (String): the class that all template models should extend
@@ -125,8 +125,8 @@ For each named configuration, the following options can be configured:
   * `outputDir` (Path): the directory where rocker will generate the Java sources into
   * `classDir` (Path): the directory where the hot reload feature will compile classes to at runtime
 
-> Warning: do not configure any of `templateDir`, `outputDir`, and `classDir` to point to the same directory or to a directory that also contains other content.  
- 
+> Warning: do not configure any of `templateDir`, `outputDir`, and `classDir` to point to the same directory or to a directory that also contains other content.
+
 # Invocation
 
 ## Invoke rocker task
@@ -140,6 +140,7 @@ You can find a self-contained example build script [here](example).
 
 # Changelog
 
++ 1.0 - Made Gradle 5.0 the minimum compatible version and replaced usage of deprecated APIs.
 + 0.4 - Removed wiring between `clean` task and deleting generated Rocker sources, uses Rocker 1.2.0 by default.
 + 0.3.1 - Fixed incremental template compilation.
 + 0.3 - Incremental template compilation, i.e. only the modified templates are compiled.

example/build.gradle

@@ -1,13 +1,13 @@
 plugins {
-    id 'nu.studer.rocker' version '0.4'
+    id 'nu.studer.rocker' version '1.0'
     id 'java'
 }
 
 repositories {
     jcenter()
 }
 
-rockerVersion = '0.20.0'
+rockerVersion = '1.2.2'
 
 rocker {
     main {