[MGNLEE-274] Make sure workflow doesn't run (or use resources) unnecessarily on public instances Created: 14/May/13  Updated: 26/Jul/13  Resolved: 04/Jul/13

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 5.0.4
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLWORKFLOW-79 Make sure workflow doesn't run (or us... Closed
causality
caused by MGNLEE-271 Create basic M5 EE bundle (CE + licen... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Title was - "Update magnolia_control.sh (.bat) to remove workflow modules from Public instance on install"
Description was - The installer copies the whole Author instance, but so far we don't want to run workflow modules on public instance. So the magnolia-module-workflow-*.jar and META-INF/context.xml files should be removed from the public instance (or at least renamed, to prevent their use).



 Comments   
Comment by Magnolia International [ 04/Jul/13 ]

This is not how the workflow should be disabled on public instances (if it should). In production, one will (should) deploy the exact same war file in all environment (that's why we have "1-war-multiple-configuration" features).

Reopening - and changing the issue title !

Comment by Magnolia International [ 04/Jul/13 ]

This needs to be solved by the workflow module itself. See MGNLWORKFLOW-79.

Comment by Magnolia International [ 26/Jul/13 ]

Removing fixVersion since this has nothing to do with the EE bundle per se.

Generated at Mon Feb 12 05:28:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.