Hi, On Wed, Feb 21, 2018 at 2:47 PM, Ioan Eugen Stan <ieu...@netdava.com> wrote: > ...I saw that I need to implement > |SlingRepositoryInitializer that brings in Sling API, which I shouldn't > need....
I think you can bypass that requirement. If you look at the RepositoryInitializer.processRepository method [1] the gist is parsing the statements and using JcrRepoInitOpsProcessor to process the result. However, as running outside of Sling hasn't been a requirement so far, I suppose there might be non-essential dependencies that get in the way of doing that, but depending on your environment they might not matter, maybe you just won't be able to use certain non-essential classes. The alternative is to extract the pure JCR parts out of the jcr repoinit bundle, if you need that I think that would be a useful contribution. You're right that technically the JCR parts of this belong to the Oak level, but as it's the Sling community which needed that the modules have been created here for convenience. -Bertrand [1] https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/master/src/main/java/org/apache/sling/jcr/repoinit/impl/RepositoryInitializer.java
