jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2097) Broke lock tests in jcr2spi after the JCR 2.0 upgrade
Date Fri, 08 May 2009 09:23:45 GMT

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

angela commented on JCR-2097:

isn't this a duplicate of JCR-2004 Update SPI locking to match JCR 2.0
from my point of view it doesn't make too much sense to create bugs for all the failing tests
as long as jcr2spi, the spi and
its implementation are not adjusted to work with JCR 2.0

> Broke lock tests in jcr2spi after the JCR 2.0 upgrade
> -----------------------------------------------------
>                 Key: JCR-2097
>                 URL: https://issues.apache.org/jira/browse/JCR-2097
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.0.0
> My changes during the JCR 2.0 upgrade have broken the following tests in spi2jcr:
>     org.apache.jackrabbit.test.api.lock.LockTest
>     org.apache.jackrabbit.jcr2spi.lock.SessionScopedLockTest
> I'll mark them as known issues for now to get the Hudson build back up again, but will
continue looking at what I did to cause this breakage.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message