[MAGNOLIA-5070] Commands seems to be registered in all catalogs Created: 31/May/13  Updated: 28/Jun/13  Resolved: 26/Jun/13

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

Type: Bug Priority: Critical
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
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

 Description   

It is either a bug in the CommandsManager or the CommandsManagerTest, but if you add a new catalog with a different command to the test's setUp() method, the testRegisterCommands fails and the new command appears in all catalogs.



 Comments   
Comment by Jozef Chocholacek [ 26/Jun/13 ]

Fixed alongside with MAGNOLIA-4820 in https://git.magnolia-cms.com/gitweb/?p=magnolia_main.git;a=commitdiff;h=ab79869a9cd93b41f6f192741ffd299e562edef0

The bug was in the test setup.

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