[MGNLCAMPU-13] Don't bootstrap bootstrap files for modules which are optional when they are not presented in webapp Created: 17/Mar/15  Updated: 30/Mar/15  Resolved: 26/Mar/15

Status: Closed
Project: Campaign Publisher
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

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

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
Date of First Response:

 Description   

For example dam module is just optional, but config.modules.dam-app.apps.assets.subApps.browser.actionbar.sections.asset.groups.activationActions.items.selectCampaignAction.xml bootstrap file is bootstrapped also when dam module is not presented in webapp.



 Comments   
Comment by Roman Kovařík [ 23/Mar/15 ]

Please use info.magnolia.module.delta.ModuleDependencyBootstrapTask

Comment by Jaroslav Simak [ 26/Mar/15 ]

Reopened:
Nothing is bootstrapped into the configuration (there is no entry in app launcher, no campaign actions in assets app, pages app, etc.)

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