[ http://jira.magnolia.info/browse/MAGNOLIA-1353?page=comments#action_13588 ] Fabrizio Giustina commented on MAGNOLIA-1353: ---------------------------------------------
a generic note on the problems with bootstrapping content into /server from modules (is discussed here and in a couple of other issues) I agree that modules should probably only bootstrap things in /modules, but I would also like to avoid putting anything in WEB-INF/bootstrap which should be a default configuration. IMHO everything that is a default should be embedded in jars (easy project setup, easy migration), but should be overwritable by user files in WEB-INF/bootstrap. Maybe we should define a bootstrapped directory in core with this items? That directory would be bootstrapped BEFORE user files and modules so content will always be overridden by custom configuration. The goal should be the magnolia could bootstrap and work with default settings also WITHOUT putting anything in WEB-INF/bootstrap > bootstrapping: custom mime types are not bootstrappable > ------------------------------------------------------- > > Key: MAGNOLIA-1353 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1353 > Project: Magnolia > Issue Type: Bug > Components: core > Affects Versions: 3.0.1 > Reporter: Philipp Bracher > Assigned To: Sameer Charles > Fix For: 3.0.2 > > > The bootstrapp file for the server/MIMEMapping is for no reason in the admin > interface module. This prohipits having own mimetype bootstrap files in the > bootstrap folder of the webapp or in other modules. -- 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/developer.html ----------------------------------------------------------------
