Migrate JCR Browser app to new framework
(MGNLUI-5759)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.3 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Sang Ngo Huu | Assignee: | Sang Ngo Huu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 5.45h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Sprint: | UI FW 3, UI FW 4, UI FW 5, UI FW 6, UI FW 7, UI FW 8 |
| Description |
|
Options:
|
| Comments |
| Comment by Šimon Demočko [ 10/Jun/20 ] |
|
czimmermann Can we, business-wise, consider JCR browser app as a feature rather than part of framework and change underlying implementation deliberately? |
| Comment by Christopher Zimmermann [ 10/Jun/20 ] |
|
Can you outline what those options would be mean concretely - not sure I get the question 100%. But I can say we must expect that some customers have customized the JCR app, for example adding actions etc. So, when we replace with M6 implementation, we need to also have an M5 version available - following the same pattern as the other apps. Ideally not bundled, but ready to be included - and documentation on how to do it. With the above, I would be OK with making the switch on the 6.2 series. I would not consider it a breaking change since a customer can "opt out" and install the old browser if they choose. |
| Comment by Roman Kovařík [ 03/Aug/20 ] |
|
sang.ngo could you summarise what was actually done? |
| Comment by Adam Siska [ 03/Aug/20 ] |
|
Please see also this: https://jira.magnolia-cms.com/browse/MGNLUI-5938?focusedCommentId=227733 |
| Comment by Sang Ngo Huu [ 04/Aug/20 ] |
|
We don't bundle old app into ce. Users can get it from nexus and install it by themselves. |