jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-602) VersionManager is never updated
Date Tue, 07 May 2013 09:51:16 GMT

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

Marcel Reutegger resolved OAK-602.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8

Enabled test with http://svn.apache.org/r1479831

No change to the versioning code was needed. The issue was probably fixed by other changes.
                
> VersionManager is never updated
> -------------------------------
>
>                 Key: OAK-602
>                 URL: https://issues.apache.org/jira/browse/OAK-602
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: jcr
>            Reporter: angela
>            Assignee: Marcel Reutegger
>             Fix For: 0.8
>
>
> the following test fill will always fail as the version manager
> has been created before:
> {code}
> @Test
>     public void testGetVersionHistory() throws Exception {
>         testRootNode.addMixin(JcrConstants.MIX_VERSIONABLE);
>         superuser.save();
>         VersionHistory vh = versionManager.getVersionHistory(testRoot);
>     }
> {code}
> however, it will succeeed if the version manager instance is created
> *after* the save call.

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

Mime
View raw message