[MGNLADMLEG-18] VersionCommand saves comment property to MetaData Created: 04/Dec/12  Updated: 04/Jul/13  Resolved: 02/Jul/13

Status: Closed
Project: Admininterface Legacy 4.x (closed)
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.0.1

Type: Task Priority: Critical
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3409 Wrong comment is used when restoring ... Closed
is related to MAGNOLIA-4473 Restore command does not restore the ... Closed
is related to MAGNOLIA-4697 Comment is not deleted from metadata ... Closed
is related to MGNLDMS-253 CLONE -Wrong comment is used when res... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

MetaData are not supported in Magnolia 5.0 any more. But VersionCommand used metada for store version comment. This must be refactored to make version command working again.

After migration of VersionCommand related issues should be ported to 5.0



 Comments   
Comment by Milan Divilek [ 02/Jul/13 ]

Issue was already solved. VersionCommand use info.magnolia.jcr.util.NodeTypes.Versionable.COMMENT.

Tickets MAGNOLIA-4473 and MAGNOLIA-4697 were solved in MAGNOLIA-4784 (fixed VersionCommand was move into core).

Port of MAGNOLIA-3409 done in this ticket.

Generated at Sun Feb 11 23:08:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.