Re: mountByFS and Initial Content Loader

2010-01-07 Thread Vidar Ramdal
>> > Vidar Ramdal wrote: >> >> However, the mountByFS feature relies on the Sling-Initial-Content >> >> header to decide which paths should be mapped. This crashes with the >> >> Sling Content Loader bundle, which also looks for that header. So, if >> >> the Content Loader bundle is active when you

Re: mountByFS and Initial Content Loader

2010-01-06 Thread Justin Edelson
On Wed, Jan 6, 2010 at 8:53 AM, Vidar Ramdal wrote: > > Vidar Ramdal wrote: > >> However, the mountByFS feature relies on the Sling-Initial-Content > >> header to decide which paths should be mapped. This crashes with the > >> Sling Content Loader bundle, which also looks for that header. So, if

Re: mountByFS and Initial Content Loader

2010-01-06 Thread Vidar Ramdal
> Vidar Ramdal wrote: >> The maven-sling-plugin has the very useful feature mountByFS, which >> automatically sets up FsResourceProviders for the initial-content in >> the bundle. >> This is great for development, as you can work directly on the files >> in the bundle, without having to re-deploy t

Re: mountByFS and Initial Content Loader

2010-01-06 Thread Carsten Ziegeler
Hi, Vidar Ramdal wrote: > The maven-sling-plugin has the very useful feature mountByFS, which > automatically sets up FsResourceProviders for the initial-content in > the bundle. > This is great for development, as you can work directly on the files > in the bundle, without having to re-deploy the

mountByFS and Initial Content Loader

2010-01-06 Thread Vidar Ramdal
The maven-sling-plugin has the very useful feature mountByFS, which automatically sets up FsResourceProviders for the initial-content in the bundle. This is great for development, as you can work directly on the files in the bundle, without having to re-deploy the bundle for each change. However,