Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1151278852.1205504307715.JavaMail.jira@brutus>
Date: Fri, 14 Mar 2008 07:18:27 -0700 (PDT)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-1475) Inconsistency when version with a
 label is removed
In-Reply-To: <379999248.1205501005620.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578749#action_12578749 ] 

Marcel Reutegger commented on JCR-1475:
---------------------------------------

Added test case, which is not enabled to run because it fails: org.apache.jackrabbit.core.version.RemoveVersionLabelTest

> Inconsistency when version with a label is removed
> --------------------------------------------------
>
>                 Key: JCR-1475
>                 URL: https://issues.apache.org/jira/browse/JCR-1475
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> While executing random operations on the version storage I came across a situation where a version is removed that has a version label.
> The current behaviour in jackrabbit is IMO not correct because the version node gets removed, but the version label is still present in the version history. This means there is a referenceable property that points to nowhere.
> So I guess either:
> - the version label property must be removed as well when the version is removed
> or
> - the remove version operation should fail because the version is still referenced
> I wasn't able to find a relevant section in the spec, though I must admit that I don't know the versioning section that well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.