#300 Updated sample project with mlSecurityUsername

examples/sample-project/build.gradle

@@ -8,7 +8,7 @@ buildscript {
 		jcenter()
 	}
 	dependencies {
-		classpath "com.marklogic:ml-gradle:3.0.0"
+		classpath "com.marklogic:ml-gradle:3.4.0"
 	}
 }
 

examples/sample-project/gradle.properties

@@ -31,20 +31,22 @@ mlRestAdminPassword=password
 
 
 # If specified, the manage username/password combo is used with the ML Management REST API for managing application
-# resources; this user must have the manage-admin and rest-admin roles.
+# resources; this user must have the manage-admin and rest-admin roles, along with the "security" role if
+# mlSecurityUsername is not specified below.
 #
 # If these are not set, then mlUsername/mlPassword is used for managing application resources.
 mlManageUsername=sample-project-manager
 mlManagePassword=password
 
 
-# If specified, the admin username/password combo is used for operations that require connecting to the Admin server
-# on port 8001. In addition, as of version 3.2.1, this username/password combo is also used for operations on the
-# Manage server on port 8002 that require the "security" role. This may be modified in a future version of ml-gradle.
+# Starting with 3.4.0, mlSecurityUsername should be set when the value of mlManageUsername is either not a user with
+# the "security" role or is a user defined within the project, in which case some existing ML user is needed to create
+# the user. See https://github.com/marklogic-community/ml-gradle/wiki/Configuring-different-users-for-different-jobs
+# for more information.
 #
 # If these properties are not set, then mlUsername/mlPassword will be used.
-mlAdminUsername=admin
-mlAdminPassword=admin
+mlSecurityUsername=admin
+mlSecurityPassword=admin
 
 
 # Configuring the number of forests for the content database (and optional test database) is a common requirement, and