[MGNLPN-384] MGNLPN-373 broke compatibility Created: 11/May/17  Updated: 18/May/17  Resolved: 17/May/17

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 1.3.4, 1.4.4
Fix Version/s: 1.3.4, 1.4.5

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLPN-373 Pages App: when editing 2 pages simul... 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
Sprint: Kromeriz 96
Story Points: 1

 Description   

1.2.x is failing in the selenium build since info.magnolia.personalization.ui.pages.dialog.ComponentEditorActionAreaPresenter#ComponentEditorActionAreaPresenter(info.magnolia.ui.dialog.actionarea.view.EditorActionAreaView, info.magnolia.objectfactory.ComponentProvider, info.magnolia.context.Context, info.magnolia.personalization.variant.VariantManager, info.magnolia.personalization.variant.EditorVariantResolver, info.magnolia.i18nsystem.SimpleTranslator, info.magnolia.personalization.ui.pages.dialog.CurrentEditorElementHolder)) cannot inject the last param since it was removed from the module descriptor.

  1. The CurrentEditorElementHolder should be removed from the ctor
  2. We should keep the mapping otherwise compatibility ctor can't work.

Generated at Mon Feb 12 06:37:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.