You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2012/11/21 17:27:58 UTC

[jira] [Created] (SLING-2672) DefaultContentImporter should replace UUID if replace is specified

Justin Edelson created SLING-2672:
-------------------------------------

             Summary: DefaultContentImporter should replace UUID if replace is specified
                 Key: SLING-2672
                 URL: https://issues.apache.org/jira/browse/SLING-2672
             Project: Sling
          Issue Type: Bug
          Components: JCR
    Affects Versions: JCR ContentLoader 2.1.6
            Reporter: Justin Edelson
            Assignee: Justin Edelson


Currently, system view imports always use IMPORT_UUID_CREATE_NEW. Logically, if :replace=true, IMPORT_UUID_REPLACE_EXISTING should be used instead.

--
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] (SLING-2672) DefaultContentImporter should replace UUID if replace is specified

Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson updated SLING-2672:
----------------------------------

    Remaining Estimate: 0h
     Original Estimate: 0h
    
> DefaultContentImporter should replace UUID if replace is specified
> ------------------------------------------------------------------
>
>                 Key: SLING-2672
>                 URL: https://issues.apache.org/jira/browse/SLING-2672
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.1.6
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: JCR ContentLoader 2.1.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Currently, system view imports always use IMPORT_UUID_CREATE_NEW. Logically, if :replace=true, IMPORT_UUID_REPLACE_EXISTING should be used instead.

--
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] (SLING-2672) DefaultContentImporter should replace UUID if replace is specified

Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502125#comment-13502125 ] 

Justin Edelson commented on SLING-2672:
---------------------------------------

changed in r1412190
                
> DefaultContentImporter should replace UUID if replace is specified
> ------------------------------------------------------------------
>
>                 Key: SLING-2672
>                 URL: https://issues.apache.org/jira/browse/SLING-2672
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.1.6
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: JCR ContentLoader 2.1.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Currently, system view imports always use IMPORT_UUID_CREATE_NEW. Logically, if :replace=true, IMPORT_UUID_REPLACE_EXISTING should be used instead.

--
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] [Resolved] (SLING-2672) DefaultContentImporter should replace UUID if replace is specified

Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson resolved SLING-2672.
-----------------------------------

    Resolution: Fixed
    
> DefaultContentImporter should replace UUID if replace is specified
> ------------------------------------------------------------------
>
>                 Key: SLING-2672
>                 URL: https://issues.apache.org/jira/browse/SLING-2672
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.1.6
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Currently, system view imports always use IMPORT_UUID_CREATE_NEW. Logically, if :replace=true, IMPORT_UUID_REPLACE_EXISTING should be used instead.

--
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] (SLING-2672) DefaultContentImporter should replace UUID if replace is specified

Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson updated SLING-2672:
----------------------------------

    Fix Version/s: JCR ContentLoader 2.1.8
    
> DefaultContentImporter should replace UUID if replace is specified
> ------------------------------------------------------------------
>
>                 Key: SLING-2672
>                 URL: https://issues.apache.org/jira/browse/SLING-2672
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.1.6
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: JCR ContentLoader 2.1.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Currently, system view imports always use IMPORT_UUID_CREATE_NEW. Logically, if :replace=true, IMPORT_UUID_REPLACE_EXISTING should be used instead.

--
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