[MGNLGROOVY-73] Wrap old UI as Magnolia5 app Created: 05/Apr/13 Updated: 09/Jul/13 Resolved: 09/Jul/13 |
|
| Status: | Closed |
| Project: | Magnolia Groovy Module |
| Component/s: | None |
| Affects Version/s: | 2.0 |
| Fix Version/s: | 2.0.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Iteration 2013-14, Iteration 2013-15 | ||||||||
| Comments |
| Comment by Tobias Mattsson [ 04/Jul/13 ] |
|
Shouldn't we do this also when upgrading from 2.0 ? |
| Comment by Eric Hechinger [ 05/Jul/13 ] |
|
Register a 2.0 version handler. Even if we are currently at version 2.0.2, register this task for version 2.0 is fine. For a fresh install, --> handle by the additional install task |
| Comment by Tobias Mattsson [ 08/Jul/13 ] |
|
If someone updated from 1.2.6 to 2.0.1 they did not get these apps, when they install 2.0.2 they should get them, so the update task so not say 2.0, it should be 2.0.2. But, if someone installed 2.0.1, and then update to 2.0.2 it must not fail or overwrite them. Also, "Wrap Legacy Task" is not very descriptive, a task that wraps legace what? Make it something like "Wrap legacy pages as apps". |