#352 Updated unit-test project to use 0.11.1

Author: rjrudin

examples/unit-test-project/README.md

@@ -10,7 +10,7 @@ include this by default (not every ml-gradle user will use ml-unit-test), so it
         jcenter()
       }
       dependencies {
-        classpath "com.marklogic:ml-unit-test-client:0.11"
+        classpath "com.marklogic:ml-unit-test-client:0.11.1"
       }
     }
 
@@ -22,7 +22,7 @@ is a feature of ml-gradle for depending on packages of MarkLogic modules):
     }
       
     dependencies {
-      mlRestApi "com.marklogic:ml-unit-test-modules:0.11"
+      mlRestApi "com.marklogic:ml-unit-test-modules:0.11.1"
     }
 
 With those additions in place, the "mlUnitTest" task can be run. This task will use the value of mlTestRestPort to 

examples/unit-test-project/gradle.properties

@@ -1,5 +1,5 @@
-mlGradleVersion=3.6.3
-mlUnitTestVersion=0.11
+mlGradleVersion=3.7.1
+mlUnitTestVersion=0.11.1
 
 mlHost=localhost
 mlAppName=unit-test-example

src/main/groovy/com/marklogic/gradle/MarkLogicPlugin.groovy

@@ -283,6 +283,7 @@ class MarkLogicPlugin implements Plugin<Project> {
 		project.task("mlUnitTest", type: UnitTestTask, group: unitTestGroup, description: "Run tests found under /test/suites in the modules database. " +
 			"Connects to MarkLogic via the REST API server defined by mlTestRestPort (or by mlRestPort if mlTestRestPort is not set), and uses mlRest* properties for authentication. " +
 			"Use -PunitTestResultPath to override where test result files are written, which defaults to build/test-results/marklogic-unit-test. " +
+			"Use -PrunCodeCoverage to enable code coverage support when running the tests. " + 
 			"Use -PrunTeardown and -PrunSuiteTeardown to control whether teardown and suite teardown scripts are run; these default to 'true' and can be set to 'false' instead. ")
 
 		logger.info("Finished initializing ml-gradle\n")