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/08/16 16:53:31 UTC

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

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
            Reporter: Julian Reschke


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.

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

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ 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.

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

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520530 ] 

Marcel Reutegger commented on JCR-1065:
---------------------------------------

Sounds reasonable.

> 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
>            Reporter: Julian Reschke
>
> 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.

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

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

Julian Reschke resolved JCR-1065.
---------------------------------

    Resolution: Fixed

Fixed as discussed with revision 567054.



> 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
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>
> 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.

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

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520543 ] 

Marcel Reutegger commented on JCR-1065:
---------------------------------------

The obvious approach to throw a NotExecutableException sounds reasonable to me. Should have been more precise...

> 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
>            Reporter: Julian Reschke
>
> 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.

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

Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520534 ] 

Julian Reschke commented on JCR-1065:
-------------------------------------

"Sounds reasonable" to throw the exception, or to try something else? :-)

> 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
>            Reporter: Julian Reschke
>
> 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.

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

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

Julian Reschke reassigned JCR-1065:
-----------------------------------

    Assignee: Julian Reschke

> 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
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>
> 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.