[MGNLWORKFLOW-359] Remove uses of the Content API Created: 14/Jul/17  Updated: 21/Nov/17  Resolved: 17/Aug/17

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.7

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: tech-debt
Remaining Estimate: 0d
Time Spent: 2d
Original Estimate: 2d

Issue Links:
Relates
relates to MAGNOLIA-7101 info.magnolia.module.delta.AllChildre... Open
relation
is related to DOCU-1232 Update "Workflow module" page Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: Remove Content API
Sprint: Saigon 107, Saigon 108, Saigon 109
Story Points: 3

 Description   

see https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=136852051 for further detail.



 Comments   
Comment by Mikaël Geljić [ 17/Oct/17 ]

cmeier

introduction of info.magnolia.workflow:magnolia-workflow-compatibility, but *without* maven relocation; relocation didn't make sense because "normal" workflow module already had proper coordinates.

only without the compatibility module, binary compatibility may break for one install task (...):
info.magnolia.module.workflow.jbpm.setup.MoveWorkItemHandlerRegistryTask

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