[MGNLUI-3034] BlossomFormDialogPresenter breaks due to FormDialogPresenterImpl constructor signature changing in Magnolia 5.3 Created: 01/Jul/14  Updated: 09/Jul/14  Resolved: 02/Jul/14

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.3
Fix Version/s: 5.3.1

Type: Bug Priority: Blocker
Reporter: Joey Bartram Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by BLOSSOM-180 Blossom Incompatible with Magnolia 5.3 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

The constructor for FormDialogPresenterImpl has two new parameters for AvailabilityChecker and ContentConnector. The call to super from the constructor for BossomFormDialogPresenter does not contain these parameters causig a java.lang.NoSuchMethodError exception.

Blossom does not work at all with Magnolia 5.3, version 3.0, 3.0.1, 3.0.2 are affected.


Generated at Mon Feb 12 09:02:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.