[PUBLISHING-99] Move away from JCR node locking Created: 01/Mar/21  Updated: 22/Aug/22  Resolved: 30/Apr/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.9, 1.2.6

Type: Task Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 1h
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes EEPUBLISH-37 Publication fails on Windows machines... Closed
causes PUBLISHING-122 Publication fails on Windows machines... Closed
Relates
relates to PUBLISHING-109 Concurrent modification of same nodes... Closed
dependency
is depended upon by EEPUBLISH-28 Recurring Problem With Node Locking A... Closed
documentation
to be documented by PUBLISHING-108 DOC: JCR node locking as a fall back ... Closed
relation
is related to PUBLISHING-86 Provide an app to clear activation locks Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Nucleus Quality Maintenance
Sprint: HL & LD 23, HL & LD 24, HL & LD 25, HL & LD 26, HL & LD 27, HL & LD 28
Story Points: 8
Team: Nucleus

 Description   

See EEPUBLISH-28 for more details about the lock issue.

This ticket aim is to provide new implementation for locks.



 Comments   
Comment by Simon Tourville [ 09/Jun/21 ]

Please add somewhere in the docs this info:
https://jira.magnolia-cms.com/browse/SUPPORT-13165

So, developpers under Windows must absolutly configuge this very hidden parameter to go back to the previous config. You'll get lot of support requests about this one I guess.

Comment by Jaroslav Simak [ 09/Jun/21 ]

Hi Simon,

info about the workaround should appear in the Known Issues section in a couple of minutes.

Thank you.

Generated at Mon Feb 12 10:35:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.