[MAGNOLIA-768] New Modules Mechanism Created: 15/Mar/06  Updated: 23/Jan/13  Resolved: 16/Nov/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 3.0 Final

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-761 Modules Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-770 create samples module Sub-task Closed Magnolia International  
MAGNOLIA-771 remove all content from the web module Sub-task Closed Philipp Bärfuss  
MAGNOLIA-772 facilitate developement Sub-task Closed Philipp Bärfuss  
MAGNOLIA-773 no JSP for the admintemplates Sub-task Closed Philipp Bärfuss  
MAGNOLIA-774 improve repository registration Sub-task Closed Philipp Bärfuss  
MAGNOLIA-775 restart system page Sub-task Closed Boris Kraft  
MAGNOLIA-776 update module documentation Sub-task Closed Boris Kraft  
MAGNOLIA-777 XML Schema for module descriptors Sub-task Closed  
MAGNOLIA-779 clean up modules node (naming, ...) Sub-task Closed Philipp Bärfuss  
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:

 Description   

I was not able to make a maintask out of the concepts subtask Therefore I created a new one. You find the details in the linked task



 Comments   
Comment by Philipp Bracher [ 15/Mar/06 ]

The original task

Comment by Philipp Bracher [ 21/Mar/06 ]

we need a subfolder in mgnl-bootstrap for each module this avoids the regisration of the additional files in the descriptor on avoids cross loading:

if the module workflow has a config.modules.adminInterface.config.menu.inbox file it is loaded during the registration of the adminInterface module.

It's easier to change it now.

Comment by Philipp Bracher [ 17/May/06 ]

This is a main tasks an not scheduled itself

Comment by Philipp Bracher [ 17/May/06 ]

The new module mechanism intoduced in 3.0

Comment by Magnolia International [ 16/Nov/07 ]

This was actually done for 3.0
Revised for 3.5
Individual sub tasks have their specific version set.

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