[MAGNOLIA-2979] workflow should not depend on the samples: it should not perform extra installation tasks Created: 17/Dec/09  Updated: 03/Dec/13  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: samples, workflow
Affects Version/s: 4.2.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-3258 installation/update: execute tasks af... Closed
relation
is related to MAGNOLIA-2978 workflow: editors group has assigned ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

The modifications done if both modules are present, should be performed by the samples.



 Comments   
Comment by Philipp Bärfuss [ 17/Dec/09 ]

Postponed to later releases. See comment added to info.magnolia.module.workflow.setup.WorkflowModuleVersionHandler.

The main issue is that both modules: samples and workflow depend on the editors group. Both modules should test the existence and then add or update that group independently.

Comment by Philipp Bärfuss [ 03/Dec/13 ]

Since M5 we support a new workflow integration and don't plan to maintain the old one further.

Generated at Mon Feb 12 03:42:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.