[MAGNOLIA-6937] Remove VersionUtil usage from content-decorators Created: 26/Jan/17 Updated: 15/Dec/17 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Espen Jervidalo | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | jcr-util core-split |
| Story Points: | 8 |
| Description |
|
This will need some concepting. We should not use our own VersionUtil inside an otherwise magnolia-agnostic wrapper.. maybe inject the version-resolve-srtategy upon instantiation? May also be that this one should be tackled together with version-extraction. But it was in the way of the jcr-split as well.. |