[ http://jira.magnolia.info/browse/MAGNOLIA-772?page=comments#action_11780 ]
Philipp Bracher commented on MAGNOLIA-772: ------------------------------------------ magnolia.develop property introduced it works already for the resources (js, css, ...) No solution yet for the jsps > facilitate developement > ----------------------- > > Key: MAGNOLIA-772 > URL: http://jira.magnolia.info/browse/MAGNOLIA-772 > Project: magnolia > Type: Sub-task > Reporter: Philipp Bracher > Assignee: Philipp Bracher > Fix For: 3.0 Final > > > 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: > -------------- > The javascript files are streamed from the resources and therefore cached. If > the property is true we read the files directly from the classes directory > instead of using getResourceAsStream(). > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
