concept for future magnolia (possibly 3.5)
(MAGNOLIA-587)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface, core |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 Beta 1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
We have done the major step for modularizing magnolia. I would like go a step further before we release 3.0. Goal
Changes
B) Templates , .. per module
C) remove admindocroot and admintemplates
D) New module definition no longer in the manifest file
E) subdir per module
NO JSP in the admin interfaces |
| Comments |
| Comment by Fabrizio Giustina [ 03/Mar/06 ] |
|
some actions takes on C) remove admindocroot and admintemplates: |
| Comment by Philipp Bracher [ 03/Mar/06 ] |
|
F) Restart after installation
|
| Comment by Philipp Bracher [ 13/Mar/06 ] |
|
I have changed the following (not yet checked in): Better initialization process:
Module definition:
Default module:
Observation:
Configurable:
Resources:
|
| Comment by Philipp Bracher [ 13/Mar/06 ] |
|
and not to forget: killed a lot of static methods |
| Comment by Boris Kraft [ 13/Mar/06 ] |
|
Did anybody ever think of uninstalling modules again?
I think it would be nice to have something like a module section in adminCentral that shows installed modules and allows us to uninstall or install a module at runtime. How much overlapü is there with Ralfs new deployment mechanism? |
| Comment by Ralf Hirning [ 13/Mar/06 ] |
|
Yes there is an overlap, but I would like to have both. We can combine them and use packaging to install a module. Deployment: It would be nice if we could omit the restart |
| Comment by Philipp Bracher [ 13/Mar/06 ] |
|
I think it will take time to consolidate both. Therfore I propose to use the system as it is (with my changes and your packaging module) for the next relase. Modules: for magnolia / modules developers Packages: for templaters, system administrators, ... I think both can provit from each other if we handle it clever enough. the module mechanism brings:
The packaging brings:
Perhaps we should meet (virtual or real) after the next release to consolidate this |
| Comment by Philipp Bracher [ 15/Mar/06 ] |
|
I commited the main code: Lifecycle:
Module Descriptor (betwixt used to read the modules xml descriptor):
ObservedManager (reloading after a registered node changed)
Default Modoule Implementation: AbstractModule
I will add subtasks to define the open points. |
| Comment by Philipp Bracher [ 15/Mar/06 ] |
|
Is now |