[BLOSSOM-246] Remove uses of the Content API Created: 11/Oct/17 Updated: 15/Apr/20 Resolved: 29/Oct/19 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.1 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Federico Grilli |
| Resolution: | Done | 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
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Epic Link: | Remove Content API | ||||||||
| Sprint: | Release 6.1.3 & Content API RM | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
In order to be able to migrate to Vaadin 8 a preliminary fix was added to the blossom module. We should however properly phase out the classes containing Content API. For more details see linked page. |
| Comments |
| Comment by Philip Mundt [ 11/Oct/17 ] |
|
Content API removal |