[ https://issues.apache.org/jira/browse/SLING-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404077#comment-15404077 ]
Oliver Lietz commented on SLING-5943: ------------------------------------- [~bdelacretaz], did you see my comment on dev@? {quote} How about supporting multiple repoinit sources? So instead of String property text.url a String[] property text.urls (URL prefixed with text format): model:context:/resources/provisioning/model.txt raw:classpath://com.example.sling.repoinit/repoinit.txt That would allow using default repoinit statements and custom ones without putting all in one source. {quote} We could use {{@}} or {{|}} to name the section, e.g.: {{model@repoinit:context:/resources/provisioning/model.txt}} > Support explicit format in jcr.repoinit.RepositoryInitializer configuration > ---------------------------------------------------------------------------- > > Key: SLING-5943 > URL: https://issues.apache.org/jira/browse/SLING-5943 > Project: Sling > Issue Type: Improvement > Components: JCR > Affects Versions: Repoinit JCR 1.0.0 > Reporter: Bertrand Delacretaz > Assignee: Bertrand Delacretaz > Priority: Minor > Fix For: Repoinit JCR 1.0.2 > > Attachments: repoinit-config.jpg > > > As suggested by [~olli] in SLING-5923 it makes sense to have an explicit { > raw, provisioning model } format for the repoinit statements that the > {{RepositoryInitializer}} uses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)