#454 Better example in provider project

examples/dependency-project/dhf-client-project/build.gradle

@@ -6,7 +6,7 @@ buildscript {
 		}
 	}
 	dependencies {
-		classpath "gradle.plugin.com.marklogic:ml-gradle:3.13.0"
+		classpath "gradle.plugin.com.marklogic:ml-gradle:3.14.0"
 		classpath "gradle.plugin.com.marklogic:ml-data-hub:4.2.2"
 	}
 }

examples/dependency-project/ml-gradle-client-project/src/main/ml-config/databases/content-database.json

@@ -3,12 +3,12 @@
 	"schema-database": "%%SCHEMAS_DATABASE%%",
 	"range-element-index": [
 		{
-			"collation": "",
+			"collation": "http://marklogic.com/collation/",
 			"invalid-values": "reject",
-			"localname": "amount",
+			"localname": "applicationSpecificId",
 			"namespace-uri": "",
 			"range-value-positions": false,
-			"scalar-type": "double"
+			"scalar-type": "string"
 		}
 	]
 }

examples/dependency-project/provider-project/src/main/ml-config/databases/README.md

@@ -0,0 +1,5 @@
+This example shows how a bundle provider can contribute a range index to an application-specific database. The token 
+"%%DATABASE%%" is used, which will be populated by ml-gradle by the main content database name (on a Data Hub project, 
+this will be the name of the final database). The file could reference any property though - e.g. a provider may wish 
+to require a property such as "acmeDatabaseName", and the client of the provider would need to set that property e.g. 
+in gradle.properties so that it's correctly replaced at deployment time. 

examples/dependency-project/provider-project/src/main/ml-config/databases/provider-database.json

@@ -2,12 +2,12 @@
 	"database-name": "%%DATABASE%%",
 	"range-element-index": [
 		{
-			"collation": "http://marklogic.com/collation/",
+			"collation": "",
 			"invalid-values": "reject",
-			"localname": "providerId",
+			"localname": "amount",
 			"namespace-uri": "",
 			"range-value-positions": false,
-			"scalar-type": "string"
+			"scalar-type": "double"
 		}
 	]
 }