[
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030691#comment-16030691
]
Julian Reschke edited comment on JCR-3901 at 12/14/17 3:39 PM:
---------------------------------------------------------------
trunk: [r1796980|http://svn.apache.org/r1796980]
2.14: [r1807264|http://svn.apache.org/r1807264]
2.12: [r1809958|http://svn.apache.org/r1809958]
2.10: [r1811708|http://svn.apache.org/r1811708]
2.8: [r1818148|http://svn.apache.org/r1818148]
was (Author: reschke):
trunk: [r1796980|http://svn.apache.org/r1796980]
2.14: [r1807264|http://svn.apache.org/r1807264]
2.12: [r1809958|http://svn.apache.org/r1809958]
2.10: [r1811708|http://svn.apache.org/r1811708]
> 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
> Labels: candidate_jcr_2_6
> Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 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)
