[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka updated MAGNOLIA-2595:
----------------------------------

    Fix Version/s: 4.3.x
                       (was: 4.3.2)

> Update tasks : streamline class names, functionality and provide a couple 
> more useful abstractions
> --------------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2595
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2595
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core, updatemechanism
>            Reporter: Grégory Joseph
>            Assignee: Grégory Joseph
>             Fix For: 4.3.x
>
>
> * 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to