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

Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/08/08 12:33:50 UTC

[jira] [Updated] (JCR-3642) Ambiguous exception expectation in SessionMoveVersionExceptionTest and WorkspaceMoveVersionExceptionTest

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

Marcel Reutegger updated JCR-3642:
----------------------------------

    Summary: Ambiguous exception expectation in SessionMoveVersionExceptionTest and WorkspaceMoveVersionExceptionTest  (was: Ambiguous exception expectation in SessionMoveVersionExceptionTest )

The same problem is present in WorkspaceMoveVersionExceptionTest.
                
> Ambiguous exception expectation in SessionMoveVersionExceptionTest and WorkspaceMoveVersionExceptionTest
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-3642
>                 URL: https://issues.apache.org/jira/browse/JCR-3642
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>    Affects Versions: 2.7
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> The exception expectation in testSessionMoveSourceCheckedInVersionException() is ambiguous.
> Session.move() attempts to move a checked in node to a destination where a node already exists. For either case an exception is specified (VersionException and ItemExistsException), but the spec does not say which one takes precedence.
> The test should therefore try to move the node to a location where no node exists.

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