You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/11/11 17:29:19 UTC
[jira] [Resolved] (JCR-3692) MoveAtRootTest fails and is not
included in test suite
[ https://issues.apache.org/jira/browse/JCR-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-3692.
-------------------------
Resolution: Fixed
Committed revision 1540762.
> 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 revision.
> 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
(v6.1#6144)