jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3692) MoveAtRootTest fails and is not included in test suite
Date Mon, 11 Nov 2013 16:08:17 GMT

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

Bertrand Delacretaz commented on JCR-3692:

FWIW, I forgot to mention explicitly in this issue's description that MoveAtRootTest is currently
not executed in builds, and was not for 2.6.4 either, as it's not included in o.a.j.core/TestAll.java
- the attached patch fixes this.

> MoveAtRootTest fails and is not included in test suite
> ------------------------------------------------------
>                 Key: JCR-3692
>                 URL: https://issues.apache.org/jira/browse/JCR-3692
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Bertrand Delacretaz
>            Assignee: angela
>            Priority: Minor
>         Attachments: activate-moveatroot.patch
> The MoveAtRootTest introduced by JCR-2680 fails when executed against the current jackrabbit-core
trunk (mvn clean test -Dtest=MoveAtRootTest), with "javax.jcr.RepositoryException: Attempt
to remove/move the admin user".
> The operation that fails is Session.move("/MoveAtRootTest_A", "/MoveAtRootTest_B")
> AFAICS this is caused by the JCR-3686 changes. The same test passes on the http://svn.apache.org/repos/asf/jackrabbit/tags/2.6.4
> I'll attach a patch that includes the test in the core test suite. If there's a good
reason to forbid such a move, it should be documented and the test changed to reflect the
expected behavior.

This message was sent by Atlassian JIRA

View raw message