[MAGNOLIA-5318] Tool to help with migration of existing objects Created: 16/Sep/13 Updated: 08/Mar/19 Resolved: 08/Mar/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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: | |||||||||
| Epic Link: | language bundles | ||||||||
| Description |
|
The tool should analyze a given object and ideally
The 1 point can be realized by further instrumenting objects via a subclass of the i18nizer. The last 2 points are unfortunately probably hard to achieve without instrumenting Node2Bean (so we can know where a given Java property comes from in JCR, since it won't necessarily be a 1:1 mapping (references and extends)) |
| Comments |
| Comment by Magnolia International [ 16/Sep/13 ] |
|
A prototype has been committed for |
| Comment by Daniel Lipp [ 02/Jul/14 ] |
|
Set unassigned and open as nobody will tackle soon. |
| Comment by Mikaël Geljić [ 08/Mar/19 ] |
|
most old-style dialogs with i18nBasenames have been phased out long ago; unclear which objects left would be worth a migration by now. |