Open
Description
#609 calls out that it can be confusing to know what ml-gradle task to attach a custom task to. An assumption is often made that a task such as mlDeploy
depends on the many other mlDeploy*
tasks in ml-gradle, though this is not the case - each task is a separate entry point for selecting a set of resources to deploy. We need some documenting in the Wiki page for writing custom tasks to describe how to attach a custom task to ensure that it's always run when needed.