Incorporate UI framework improvements into the platform (MGNLUI-4487)

[MGNLUI-4488] Resolve/contemplate potential circular dependency between deprecated and non-deprecated artifacts Created: 11/Jul/18  Updated: 02/Aug/18  Resolved: 02/Aug/18

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

Type: Sub-task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Sprint: Basel 151, Basel 152, Basel 153

 Description   

Example:

  • We would like move most of the content app classes to compatibility package.
  • However, we would probably like to keep the location classes (DetailLocation/BrowserLocation) not deprecated.
  • At least DetailLocation, however, references a deprecated class (DetailView).
  • Some deprecated classes though definitely reference DetailLocation.

We anyway contemplate to keep an unconditional dependency in UI on compatibility artifact, but the situation above requires that the* compatibility layer also depends on the current UI*. This creates a circular dependency which needs to be addressed.



 Comments   
Comment by Aleksandr Pchelintcev [ 02/Aug/18 ]

At the moment, only compatibility artifact depends on the ui-framework, not the other way around.

*NOTE*: in order to achieve that vaadin-integration sub-module had to be preserved in order to be able to allow the old actions (and potentially other abstractions like availability rules, column formatters etc) to be executed in Vaadin 8 based apps.

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