[MGNLPN-450] Migrate personalization-integration to new UI framework Created: 31/Oct/19  Updated: 12/Dec/19  Resolved: 29/Nov/19

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Story Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 2h 56m
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPN-447 Migrate component personalization to ... 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)
Epic Link: Migrate apps to new UI framework
Sprint: UI Framework 11, UI Framework 12
Story Points: 8

 Description   
  • Create personalization-core submodule
  • move non UI classes from personalization-integration into this module
  • move ui classes into personalization-compatibility
    • info.magnolia.personalization.action
    • info.magnolia.personalization.column
    • info.magnolia.personalization.editor.pagebar.variantselector
    • info.magnolia.personalization.ui
  • get rid of JcrItemId from info.magnolia.personalization.registry.variant
  • integrate p13n into new pages app

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