[MGNLMAIL-67] Split out app functionalities into a separated modules Created: 08/Jun/15  Updated: 24/Mar/22

Status: Open
Project: Magnolia Mail Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance
Remaining Estimate: 0.75d
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLOBS-33 Magnolia module descriptor depends on... Open
relates to MGNLMAIL-62 Synchronize dependency in pom.xml and... Closed
relates to MGNLMAIL-42 Remove obsolete mail templates Closed
causality
is causing MGNLIMG-161 Optional dependency to site module in... Closed
is causing PSWDMNGR-12 Split Password manager module into co... 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)
Date of First Response:

 Description   

One known problem is observation module having a dependency to mail module, which pulls in admincentral.

See linked ticket.



 Comments   
Comment by Viet Nguyen [ 03/Aug/18 ]

We'll consider split mail module into mail-support (as mail-core), mail-template and mail-app for separation of concerns and easily split out instances into Micro public instance

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