[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:
supersession
is superseded by MAGNOLIA-5318 Tool to help with migration of existi... Closed
Template:
Acceptance criteria:
Empty
Epic Link: language bundles
Sprint: 5.1 - Final

 Description   

The tool should analyze a given object and ideally

  1. modify/create message bundle files (based on existing translations with non-standard keys, hard-configured texts, ...)
  2. generate a list of jcr properties "to be deleted" - which could be used for update tasks
  3. re-generate the bootstrap file where this object was originally configured

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

  • Using a script and passing it an object to "inspect". See info.magnolia.i18nsystem.tools.GenerateTranslationFilesImpl
  • By replacing the system implementation of info.magnolia.i18nsystem.I18nizer by info.magnolia.i18nsystem.tools.ToolingProxytoysI18nizer (can be configured via magnolia.properties for example)

Follow-up task is in MAGNOLIA-5300

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