[MAGNOLIA-5300] Prototype tool to help with migration of existing objects Created: 05/Sep/13 Updated: 02/Oct/13 Resolved: 17/Sep/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Epic Link: | language bundles | ||||||||
| Sprint: | 5.1 - Final | ||||||||
| 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, which keeps track of "tasks" to do while navigating the UI. It can be used in two ways
Follow-up task is in |