[MGNLDAM-602] Revert deprecation of DamConfig Created: 14/Jul/15  Updated: 08/Sep/15  Resolved: 24/Jul/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM Templating
Affects Version/s: 2.0.8, 2.0.9, 2.1
Fix Version/s: 2.0.11, 2.1.1

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Trang Truong
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5d
Original Estimate: Not Specified

Issue Links:
causality
is causing BLOSSOM-216 Avoid using deprecated DamConfig for ... 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
Date of First Response:
Sprint: Sprint 2 (Vietnam), Sprint 3 (Basel)
Story Points: 1

 Description   

info.magnolia.dam.app.ui.config.DamConfig was deprecated in 2.0.8 without replacement with a statement saying it's not used. This not correct since it is used in config by code and is the way to use the DAM in Blossom projects.

The deprecation should be reverted in both 2.0.x and 2.1.x lines.



 Comments   
Comment by Trang Truong [ 24/Jul/15 ]

Revert the commit that marked deprecate. It's fixed in branch MGNLDAM-602-revertDeprecate

Generated at Mon Feb 12 05:01:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.