[MGNLUI-4491] Decide whether CKEditor related resources should be moved to compatibility artifact Created: 11/Jul/18  Updated: 20/Sep/18  Resolved: 20/Sep/18

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-4615 Integrate rich text field into Resurf... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Account:
Epic Link: UI framework implementation
Sprint: Basel 156
Story Points: 1

 Description   

Talking about .../magnolia-ui-framework/src/main/resources/mgnl-resources



 Comments   
Comment by Federico Grilli [ 17/Sep/18 ]

Those files are actually used also by the new Vaadin8 add-on and can be shared by both Vaaadin7 and Vaadin8 add ons without changes.
Therefore I'd keep them in ui-framework. The only file which is specific to the compatibility artifact is https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/pull-requests/645/diff#magnolia-ui-framework-compatibility/src/main/resources/VAADIN/js/magnolia5-link/plugin.js - basically for backward compatibility styling issues

See also https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/pull-requests/645/diff

Comment by Federico Grilli [ 20/Sep/18 ]

I daresay this can be closed.

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