[ https://issues.apache.org/jira/browse/SLING-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson updated SLING-1271: ---------------------------------- Fix Version/s: (was: Maven Sling Plugin 2.0.6) > Support mounting FsResourceProviders while avoiding loading content to JCR > -------------------------------------------------------------------------- > > Key: SLING-1271 > URL: https://issues.apache.org/jira/browse/SLING-1271 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes > Affects Versions: Maven Sling Plugin 2.0.4 > Reporter: Vidar S. Ramdal > Assignee: Vidar S. Ramdal > Priority: Minor > > As described at [1], the mountByFS [2] flag allows you to have > FsResourceProviders set up automatically on bundle deploy. However, the > Content Loader bundle still picks up the content and installs it to JCR, even > though the JCR paths are overridden by FsResourceProviders. > There are cases where you'd want to only configure FsResourceProviders, > without having the content installed to JCR. > So, we'll introduce support for another pom.xml header, called > Sling-Mount-File-Resources, which will let maven-sling-plugin setup the > FsResourceProviders, avoiding the content loader. > maven-sling-plugin will then set up FsResourceProviders if: > 1. A Sling-Mount-File-Resources element is present > -- OR -- > 2. A Sling-Initial-Content element is present, AND the mountByFS > configuration parameter is true. > [1] http://markmail.org/thread/dyytf4zmbcnnbvvr > [2] http://www.osoco.org/blog/?p=69 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira