Dear Magnolians Can someone shed some light on how the order is set up, in which bootstrap files are processed for a clean installation? I would expect to see the following:
1. Modules are installed along their order derived from the dependencies in the module descriptors. 2. Within a module: 2.1 Version handler basic install tasks 2.1.1 files in mgnl-bootstrap 2.1.2 possibly mgnl-bootstrap-samples 2.2 Version handler extra install tasks... if you have any bootstrap tasks in it And for 2.1.1 and 2.1.2 I would expect - first the less specific - then the more specific so e.g. dam.assets.xml before dam.assets.additions.xml But then, there are also the bootstrap files you can place in WEB-INF/bootstrap/.... When are those bootstrapped? What I am experiencing currently: For the same project, I get a "useful" order when the author instance is bootstrapped. When the public instance is bootstrapped however, a content is overwritten by other bootstrap files. So I'm not saying one way is right and the other is wrong. I'm just saying I'm seeing different behaviour between two instances which makes it a bit tricky to fix. So any insight is warmly appreciated! Thanks! -will -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=fae7c49a-1596-4b74-80f7-a6dc021954e4 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
