[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:
dependency
is depended upon by BLOSSOM-265 DOC: Update Blossom release page for ... Closed
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

Generated at Sun Feb 11 23:31:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.