[MAGNOLIA-7085] Provide upgrade task for replacing mapping implementations Created: 07/Jul/17 Updated: 07/Aug/17 Resolved: 04/Aug/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | Virtual URI mappings |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.6, 5.6 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Dai Ha |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 8d 2.75h | ||
| Original Estimate: | 5d | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Epic Link: | Virtual URI mappings | ||||||||||||||||||||||||||||||||
| Sprint: | Saigon 104, Saigon 105, Saigon 106, Saigon 107 | ||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||
| Description |
|
Could be in the shape of a groovy script, but ideally also usable as a "regular" version-handling Task.
|
| Comments |
| Comment by Sang Ngo Huu [ 21/Jul/17 ] |
|
Regarding a point Take one module name as input, and for that module:. I wonder why we don't take mapping path as input? We have several tickets to handler the update, I think the task should update for one path indeed and it would be:
WDYT? |
| Comment by Mikaël Geljić [ 25/Jul/17 ] |
|
`moduleName` of `modulePath` as input are both fine. Mapping paths not so much, because if you have a module declaring 100 mappings, you don't want your MVH delta to have 100 more lines / tasks. Like I suggested on the PR originally:
Additionally, class & property updates may be in the same NodeVisitorTask, that could simplify things a bit. |