Incorporate UI framework improvements into the platform
(MGNLUI-4487)
|
|
| 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 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. |