[MAGNOLIA-5023] Remove use of deprecated (Content) API from the VersionCommand Created: 10/May/13  Updated: 14/May/13  Resolved: 13/May/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: command, hardening
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Release notes required:
Yes
Sprint: Beta 2

 Comments   
Comment by Jozef Chocholacek [ 13/May/13 ]

Protected method must not be removed, but deprecated.

Comment by Jozef Chocholacek [ 13/May/13 ]

For Release Notes:
The method getFilter() now returns null, so if it is used in an inherited command, it must be overridden, too.

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