You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/09/12 18:04:32 UTC

[jira] Updated: (JCR-1120) RemoveVersionTest.testReferentialIntegrityException assumes availability of ref properties and same name sibilings

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

Julian Reschke updated JCR-1120:
--------------------------------

    Summary: RemoveVersionTest.testReferentialIntegrityException assumes availability of ref properties and same name sibilings  (was: RemoveVersionTest.testReerentialIntegrityException assumes availability of ref properties and same name sibilings)

> RemoveVersionTest.testReferentialIntegrityException assumes availability of ref properties and same name sibilings
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-1120
>                 URL: https://issues.apache.org/jira/browse/JCR-1120
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR TCK
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>
> This test case:
> - assumes availability of Reference properties (should throw NotExecutable when not available), and
> - takes advantage if same name siblings (the child node identified by the nodename2 config variable has already been created by the test setup code)

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