[MGNLUI-5973] Migrate Magnolia UI to Vaadin Flow Created: 18/Jun/20  Updated: 16/May/23  Resolved: 16/May/23

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

Type: Initiative Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: ui-devx-impr
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relation
Template:
Date of First Response:

 Description   

TODO: create the stories and tickets for the following initial problems:

  • assess the compatibility loss impact
    • see if we at least temporarily can afford the dual-version environment
    • will have to drop not jut Vaadin 7, but also Vaadin 8 support
    • research how feasible it would be to at least maybe run to versions on different servlets
  • estimate the crucial UI component coverage (including add-ons)
  • analyse impact on the theme (we use SASS still, Vaadin 16 is CSS4 based, which should be better)
  • organise KT transfer workshop re: architecture updates and features that we might use for our benefit


 Comments   
Comment by Dominik Maslanka [ 16/May/23 ]

Due to recent strategic shifts in our technical architecture approach, this epic has been marked as obsolete, as it no longer aligns with our updated objectives.

Generated at Mon Feb 12 09:31:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.