After checkout/checkin there is a stale Lockable aspect on the original node, which stops autoVersionOnUpdateProps handler from creating new versions on property changes.
Steps to reproduce:
- Create a versionable document
- Modify properties
- Edit offline
- Upload a new version
- Modify properties again
The last step should increment a version of a document, but it doesn't.
I'm using Alfresco Share to reproduce this issue.
I can actually point you to the problem in the code which causes above behaviour (line numbers are for Community 4.0.d):
1. CheckOutCheckInServiceImpl.doCheckout() first adds a Lockable aspect to original node (line 398), then copies the node (line 427) to create a working copy. Lockable aspect gets copied as well.
2. CheckOutCheckInServiceImpl.checkin() unlocks original node (line 540), but then it copies working copy back to the original (line 570), which restores Lockable aspect on the original. Lockable properties are not copied though, so they are null.
3. VersionableAspect.onUpdateProperties() policy checks if updated node has a Lockable aspect (line 434) and skips execution if true. This way new version is not created on properties update.