You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/02/22 17:23:18 UTC

[jira] [Updated] (SLING-3684) Executed commands should expose the fine-grained operations that have been performed

     [ https://issues.apache.org/jira/browse/SLING-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-3684:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.1.0)
                   Sling Eclipse IDE 1.1.2

> Executed commands should expose the fine-grained operations that have been performed
> ------------------------------------------------------------------------------------
>
>                 Key: SLING-3684
>                 URL: https://issues.apache.org/jira/browse/SLING-3684
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Robert Munteanu
>            Priority: Critical
>             Fix For: Sling Eclipse IDE 1.1.2
>
>
> Some commands, notably the AddOrUpdateNodeCommand, start having a lot of logic and can potentially perform many operations, like reodering, child node deletion and creation.
> These operations are now opaque and only visible using debug tracing. Recording these operations and making them available to the invoker would serve at least two purposes:
> # More detailed logging of what is changed ( for both users and developers )
> # Reconciling the local workspace with changes from the remote repository



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)