Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-1928] Add support for repository-only modules Created: 06/Dec/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: modulemechanism, updatemechanism
Affects Version/s: 3.5
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2265 Observe module nodes to automatically... Closed
Template:
Date of First Response:

 Description   

Currently, only modules found through a module descriptor are loaded/initialized. We should provide some level of support for user modules who merely want to group their configuration (dialogs, paragraphs, templates, ...) under a single node.
Ideally, a restart should not be needed for new modules to be picked up.

See
// TODO handle modules found in repo but not found on classpath
in ModuleManagerImpl.



 Comments   
Comment by Magnolia International [ 16/Jun/08 ]

related: any module should be observed such that adding a paragraphs or other observed nodes will register this new node with the relevant ObservedManager. -> see MAGNOLIA-2265

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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