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, 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 deploy a bundle with mountByFS, you'll end up with both FsResourceProviders AND initial content in the repository. This defies the purpose of mountByFS, and usually also leads to some unexpected behavior in resource resolution. So how about letting maven-sling-plugin support another config element in addition to Sling-Initial-Content, say, Sling-Mount-File-Resources. That way, the Content Loader bundle should not interfere when the mountByFS bundle is deployed. WDYT? -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
