Note that using cucumber.features with Gradle will run scenarios twice

Author: mpkorstanje

cucumber-junit-platform-engine/README.md

@@ -185,18 +185,23 @@ Define Cucumber properties before running the test to ensure that your `build.gr
 
 ```groovy
 tasks.test {
-    systemProperty("cucumber.features",     System.getProperty("cucumber.features"))
-    systemProperty("cucumber.filter.tags",  System.getProperty("cucumber.filter.tags"))
-    systemProperty("cucumber.filter.name",  System.getProperty("cucumber.filter.name"))
+    systemProperty("cucumber.features", System.getProperty("cucumber.features"))
+    systemProperty("cucumber.filter.tags", System.getProperty("cucumber.filter.tags"))
+    systemProperty("cucumber.filter.name", System.getProperty("cucumber.filter.name"))
+    systemProperty("cucumber.plugin", System.getProperty("cucumber.plugin"))
 }
 ```
 
 Then to select the scenario on line 10 of the `example.feature` file use:
 
 ```shell
-gradle test -Dcucumber.features="path/to/example.feature:10"
+gradle test --rerun-tasks --info -Dcucumber.plugin=pretty -Dcucumber.features=path/to/example.feature:10
 ```
 
+Note: Because both the Suite Engine and the Cucumber Engine are included, this
+will run tests twice. (If you know how to prevent this, please send a pull
+request).
+
 ## Suites with different configurations
 
 The JUnit Platform Suite Engine can be used to run Cucumber multiple times with