[
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-3901:
--------------------------------
Labels: (was: candidate_jcr_2_6)
> TCK LockManagerTest does not allow new JCR 2.0 functionality 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.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7
>
>
> 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.4.14#64029)
