[MAGNOLIA-7850] Make Commands being a definition/registry Created: 16/Jul/20  Updated: 05/Oct/23

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: 6.1.6, 6.2.1, 6.2.2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Unresolved Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
dependency
relation
is related to MAGNOLIA-4972 Commands should be able to use @Inject 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)
Date of First Response:
Epic Link: Support
Team: DeveloperX

 Description   

Rational:

Commands is the only item left, that is not a definitions/registry yet.

This has man downsides using/developing Magnolia:

  • Can only exist in JCR Configuration workspace -> pain to maintain and change
  • Can not be decorated (big downside!) and changes
  • New commands can not be added via reuse of existing ones (not custom Java, just reuse with different configurations)
  • New commands can only be brought into the system via Jar-installation/bootstrapping


 Comments   
Comment by Christopher Zimmermann [ 20/Sep/23 ]

mdivilek Can you please add a comment here with your initial findings? (Then we can unassign from you.)

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