jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
Date Wed, 23 Mar 2016 15:09:25 GMT

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

Davide Giannella updated JCR-3901:
----------------------------------
    Fix Version/s:     (was: 2.10.2)
                   2.10.3

> TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
> -----------------------------------------------------------------------
>
>                 Key: JCR-3901
>                 URL: https://issues.apache.org/jira/browse/JCR-3901
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.10.1, 2.8.1, 2.11.0
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 2.8.2, 2.10.3, 2.13.0, 2.12.2
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's always illegal
to add lock tokens to multiple sessions, however <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner>
allows simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message