You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2012/11/19 13:02:58 UTC

[jira] [Created] (OAK-453) Move move and copy methods from Root to Tree

Michael Dürig created OAK-453:
---------------------------------

             Summary: Move move and copy methods from Root to Tree
                 Key: OAK-453
                 URL: https://issues.apache.org/jira/browse/OAK-453
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: core
            Reporter: Michael Dürig
         Attachments: OAK-453.patch

In OAK-391 we decided to not track trees through moves any more (see also http://markmail.org/message/b6dcyae362akyogd). This allows us to move the {{move}} and {{copy}} methods from {{Root}} to {{Tree}} where they feel more natural. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OAK-453) Move move and copy methods from Root to Tree

Posted by "angela (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OAK-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500972#comment-13500972 ] 

angela commented on OAK-453:
----------------------------

imo the way we handle workspaces on the oak-level will have an impact on how cross-workspace
operations such as copy would be reflected and i don't want to create any fait accompli.

as far as only move is concerned i don't have a strong opinion for either variant.


                
> Move move and copy methods from Root to Tree
> --------------------------------------------
>
>                 Key: OAK-453
>                 URL: https://issues.apache.org/jira/browse/OAK-453
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>         Attachments: OAK-453.patch
>
>
> In OAK-391 we decided to not track trees through moves any more (see also http://markmail.org/message/b6dcyae362akyogd). This allows us to move the {{move}} and {{copy}} methods from {{Root}} to {{Tree}} where they feel more natural. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OAK-453) Move move and copy methods from Root to Tree

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OAK-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-453:
------------------------------

    Attachment: OAK-453.patch

Proposed patch
                
> Move move and copy methods from Root to Tree
> --------------------------------------------
>
>                 Key: OAK-453
>                 URL: https://issues.apache.org/jira/browse/OAK-453
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>         Attachments: OAK-453.patch
>
>
> In OAK-391 we decided to not track trees through moves any more (see also http://markmail.org/message/b6dcyae362akyogd). This allows us to move the {{move}} and {{copy}} methods from {{Root}} to {{Tree}} where they feel more natural. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OAK-453) Move move and copy methods from Root to Tree

Posted by "angela (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OAK-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500955#comment-13500955 ] 

angela commented on OAK-453:
----------------------------

-1 for moving copy/move to Tree as long as we didn't reach consensus on how to deal
with multiple workspace.
                
> Move move and copy methods from Root to Tree
> --------------------------------------------
>
>                 Key: OAK-453
>                 URL: https://issues.apache.org/jira/browse/OAK-453
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>         Attachments: OAK-453.patch
>
>
> In OAK-391 we decided to not track trees through moves any more (see also http://markmail.org/message/b6dcyae362akyogd). This allows us to move the {{move}} and {{copy}} methods from {{Root}} to {{Tree}} where they feel more natural. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OAK-453) Move move and copy methods from Root to Tree

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OAK-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500962#comment-13500962 ] 

Michael Dürig commented on OAK-453:
-----------------------------------

Why do workspaces block this in any other way than we have to touch stuff in {{Tree}} and {{Root}} anyway as soon as we introduce support for multiple workspaces?
                
> Move move and copy methods from Root to Tree
> --------------------------------------------
>
>                 Key: OAK-453
>                 URL: https://issues.apache.org/jira/browse/OAK-453
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>         Attachments: OAK-453.patch
>
>
> In OAK-391 we decided to not track trees through moves any more (see also http://markmail.org/message/b6dcyae362akyogd). This allows us to move the {{move}} and {{copy}} methods from {{Root}} to {{Tree}} where they feel more natural. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira