Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: updatemechanism
-
Labels:None
Description
- current naming is very inconsistent, makes it hard to find the appropriate task to use
- the way some tasks work is inconsistent with others: some are very safe (check current values, etc), some aren't (just add a property no matter what the current status is) - we should add consistency and/or document the few inconsistency and why the safety is needed in most cases
- we've often had the need for :
- tasks which recurse through subnodes - an abstract task using a Visitor would be very helpful.
- tasks which perform an operation over a given set of nodes - an abstract takes that operates on the nodes returned by a jcr query would help.
Attachments
Issue Links
- depends upon
-
MAGNOLIA-5857 Provide a NodeVisitorTask and emphasize QueryTask as "unsafe"
-
- Closed
-
- is related to
-
MAGNOLIA-2597 Provide a QueryTask - to operate on nodes returned by a given query
-
- Closed
-
