Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Fri, 8 Feb 2013 19:29:12 +0000 (UTC)
From: "Thibaut Rizzi (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12631505.1360351644097.267156.1360351752983@arcas>
In-Reply-To: <JIRA.12631505.1360351644097@arcas>
References: <JIRA.12631505.1360351644097@arcas>
Subject: [jira] [Created] (JCR-3515) After export/import, predecessors and
 baseVersion of mix:versionable node systematically points to rootVersion.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Thibaut Rizzi created JCR-3515:
----------------------------------

             Summary: After export/import, predecessors and baseVersion of mix:versionable node systematically points to rootVersion.
                 Key: JCR-3515
                 URL: https://issues.apache.org/jira/browse/JCR-3515
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: JCR 2.0, versioning
    Affects Versions: 2.4.3
            Reporter: Thibaut Rizzi
            Priority: Minor


When doing an export/import of system view XML into the same repository, jcr:predecessors  and jcr:baseVersion of mix:versionable nodes do not point to the version which was pointed at export time but to rootVersion.

For example, while in the exported XML, a node has the property baseVersion with the following value {{d1f205ad-53b8-4ed2-b74f-57cc5619108b}}. After import, baseVersion has the value {{	
cff2de16-1427-4f70-bf60-b4f424d60066}} which points to the rootVersion, even if the version with uuid {{	
d1f205ad-53b8-4ed2-b74f-57cc5619108b}} still exists in this version history.

uuid behaviour used on import is IMPORT_UUID_COLLISION_THROW.

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