And of course the obvious was right on target! Must have been in a bit of a 
hurry when set things up... 
Thanks!

-will

On 15.12.2010, at 19:06, Grégory Joseph wrote:

> 
> Hi Will,
> 
> On 15 Dec 2010, at 16:08, Will Scheidegger wrote:
> 
>> 
>> Dear Magnolians
>> 
>> I'm trying to follow the best practices, setting up a webapp project and a 
>> custom module. The custom module has a bunch of bootstrap files in its 
>> mgnl-bootstrap-samples folder and the webapp project has a dependency on it. 
>> In addition the webapp project also has 
>> 
>> magnolia.bootstrap.samples=true
>> 
>> in a custom properties file for the development server. I can tell that the 
>> custom properties file is actually used because I also changed 
>> magnolia.repositories.home and that works. However only the stuff in the 
>> mgnl-bootstrap folder gets bootstrapped. The stuff in mgnl-bootstrap-samples 
>> is ignored.
> 
> Files in there have to match this pattern - similar to regular module 
> bootstraps..
> "/mgnl-bootstrap-samples/" + moduleName + "/" ... xml
> 
> ... and similar to regular module bootstraps, this only happens on updates 
> (module version number increase) and installs.
> 
> Just thought I'd get the obvious out of the way first.
> 
>> 
>> Does anyone have an idea where to look next? Thanks!
>> 
>> -will
>> 
>> 
>> 
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to