[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2017-05-30 Thread Julian Reschke (JIRA) 

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

Julian Reschke updated JCR-3901:

Fix Version/s: 2.16

> 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.16
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2016-04-21 Thread Julian Reschke (JIRA) 

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

Julian Reschke updated JCR-3901:

Fix Version/s: (was: 2.12.2)
   (was: 2.13.0)
   (was: 2.10.3)
   (was: 2.8.2)

> 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
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2016-03-23 Thread Davide Giannella (JIRA) 

 [ 
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 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2016-02-26 Thread Davide Giannella (JIRA) 

 [ 
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.12.1)
   2.12.2

> 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.10.2, 2.8.2, 2.13.0, 2.12.2
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2016-02-09 Thread Davide Giannella (JIRA) 

 [ 
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.12.0)
   2.12.1

> 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.10.2, 2.8.2, 2.13.0, 2.12.1
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2016-02-09 Thread Davide Giannella (JIRA) 

 [ 
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.11.4)
   2.12.0
   2.13.0

> 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.10.2, 2.8.2, 2.13.0, 2.12.0
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2015-12-03 Thread Davide Giannella (JIRA) 

 [ 
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.11.3)
   2.11.4

> 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.10.2, 2.8.2, 2.11.4
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2015-10-26 Thread Davide Giannella (JIRA) 

 [ 
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.11.2)
   2.11.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.10.2, 2.8.2, 2.11.3
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2015-10-02 Thread Davide Giannella (JIRA) 

 [ 
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.11.1)
   2.11.2

> 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.10.2, 2.8.2, 2.11.2
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2015-08-21 Thread Julian Reschke (JIRA) 

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

Julian Reschke updated JCR-3901:

Affects Version/s: 2.10.1
   2.8.1

> 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.10.2, 2.8.2, 2.11.1
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2015-08-21 Thread Julian Reschke (JIRA) 

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

Julian Reschke updated JCR-3901:

Fix Version/s: 2.11.1
   2.8.2
   2.10.2

> 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.10.2, 2.8.2, 2.11.1
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



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