[MAGNOLIA-4981] Naming conflict: MessagesManager Created: 17/Apr/13 Updated: 03/Jul/14 Resolved: 03/Jul/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | 5.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Obsolete | 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)
|
| Date of First Response: |
| Description |
|
We have MessagesManager class/interface in both info.magnolia.cms.i18n (core) and info.magnolia.ui.framework.message (ui-framework) packages, each class does something else. It'd be better to rename one of it (I suggest the i18m one) to avoid misunderstandings, because there are situations when both classes are needed in the same piece of code (e.g. when sending a localized ui message to the user). |
| Comments |
| Comment by Daniel Lipp [ 03/Jul/14 ] |
|
MessagesManager in i18n has been deprecated with 5.1.1 - so it'll anyway disappear "soon"... |