New Modules Mechanism
(MAGNOLIA-768)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| 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: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
Introduce a new property magolia.developement During developement the files are not in a jar but in the classes directory (this is the main reason why the module bootsraps by default only the config.modules.modulename.* files and not every file found) Javascript: JSP We should not use JSP in the longer run for the admin templates: use the dynamically registerable page handlers instead. How ever if the developement flag is true and the system supports links it should not copy the content from classes/mgnl-content. Instead it should make links to this directories. |
| Comments |
| Comment by Philipp Bracher [ 17/Mar/06 ] |
|
magnolia.develop property introduced it works already for the resources (js, css, ...) No solution yet for the jsps |
| Comment by Philipp Bracher [ 31/Mar/06 ] |
|
Possible solutions for the jsps A) make a link to WEB-INF/classses/templates during developement time no extracting of the files B) a developer servlet (reextract the files on demand) The servlet can use a deamon to reextract by interval. I prefere B) |
| Comment by Philipp Bracher [ 12/May/06 ] |
|
first jsp redeploy page: menu->tools->deployment |