Removed OBE example of creating another database

Author: rjrudin

examples/sample-project/build.gradle

@@ -154,29 +154,6 @@ ext {
     //mlAppDeployer.commands.add(new com.marklogic.appdeployer.command.cpf.DeployDefaultPipelinesCommand())
 }
 
-
-/*
- * ml-gradle does not blindly process every file in the ml-config/databases directory. It checks for specific files
- * for a content database, a schemas database, and a triggers database. There are specific commands for each file, and
- * each command provides a number of options for configuring the forests for a database. One reason ml-gradle does not
- * blindly process every file (as opposed to doing so for every other ML resource) is that this approach would make it
- * very difficult to configure the forests for each database.
- *
- * So, if you want to create a database in addition to a content/schemas/triggers database, you'll need to add a new
- * command to do so, as shown here. Please see ml-app-deployer for more info on what you can customize on an instance
- * of DeployDatabaseCommand.
- *
- * Note also that mlDatabaseCommands is a property initialized by ml-gradle that contains a list of command objects. This
- * list is used when the "mlDeployDatabases" task is run, so it's a good idea to add a command for your custom database
- * to this list, in addition to adding it to mlAppDeployer.
- */
-ext {
-    def otherDbCommand = new com.marklogic.appdeployer.command.databases.DeployDatabaseCommand("other-database.json")
-    mlAppDeployer.commands.add(otherDbCommand)
-    mlDatabaseCommands.add(otherDbCommand)
-}
-
-
 /*
  * Example of a custom command, which in this case performs a merge on a database. The benefit of doing this in a
  * command (as opposed to a task) is that a command can be included in the mlDeploy and mlUndeploy tasks by adding it to