Adding tasks to the task registry

Each subdirectory of this directory represents a Category:

    ClusterCategory
    FailoverPolicyCategory
    MachineCategory
    ResourceCategory
    ResourceGroupCategory
    ResourceTypeCategory

or a Task Group, which is a collection of tasks displayed together
in Task Manager:

	BalanceLoadTaskGroup
	ClusterTaskGroup
	FailoverPolicyTaskGroup
	LoggingTaskGroup
	etc.

Within each of these subdirectories are files whose names
are the fully-qualified class names of tasks which are relevant
to the Category for that subdirectory, with an optional four-digit
order key and a dot ('.') prepended.  The contents of the
files are not used, so the files should be of 0 length.

When adding a task to a Category or Task Group, the Makefile for that
subdirectory needs to be updated.

A subdirectory Make will fail if any of the tasks in that directory
do not exist.  The check for task existence can be overridden by
creating an additional file that has the same name as the task with
".noerror" appended.

Example: I'm adding the task "Delete Cluster" to the task registry.
I decide that it should go into the ClusterCategory directory.  The
full name of the class that implements "Delete Cluster" is
com.sgi.fsmgr.task.DeleteClusterTask.  I want the "Delete Cluster" task
to come after the "Modify Cluster" (which has order 4000) and before the
"Define Machine" task (which has order 5000).  Please note that a string
comparison of the order keys are used, not an integer comparison.  So
be sure to use all four digits in the order key.  For example, an order
of "0999" should be used instead of "999" for a task that is to preceed
another task of order "1000".


1. cd $WORKAREA/taskRegistry/ClusterCategory
2. touch 4500.com.sgi.fsmgr.task.DeleteClusterTask
3. p_modify -f 4500.com.sgi.fsmgr.task.DeleteClusterTask
4. p_modify Makefile
5. Edit Makefile, adding 4500.com.sgi.fsmgr.task.DeleteClusterTask
   to the "TASKS" macro.
6. p_integrate
7. p_finalize