You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/09/20 20:21:31 UTC

[jira] Updated: (JCR-1065) Workspace{Copy|Move}VersionableTest assumptions on versioning

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

Jukka Zitting updated JCR-1065:
-------------------------------

    Affects Version/s: 1.2.1
                       1.2.2
                       1.2.3
                       1.3
                       1.3.1
        Fix Version/s: 1.3.2

Merged to the 1.3 branch in revision 577851.

> Workspace{Copy|Move}VersionableTest assumptions on versioning
> -------------------------------------------------------------
>
>                 Key: JCR-1065
>                 URL: https://issues.apache.org/jira/browse/JCR-1065
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR TCK
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.3.2
>
>
> These test cases assume that an ancestor of a versioned node can be made versioned. This may not be true for all JCR compliant stores.
> There should be a way to skip the test when it can not be executed.
> One obvious approach would be to throw a NotExecutableException when the attempt to enable versioning on the parent fails. However this has the drawback that it can mask configuration errors.
> Thoughts?

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