[
https://issues.apache.org/jira/browse/SLING-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650553#comment-15650553
]
Oliver Lietz commented on SLING-6263:
-------------------------------------
comment on
[dev@|https://lists.apache.org/thread.html/36718a75f4dccfb865c2dd37052593c063849ad60c6795995e786c47@%3Cdev.sling.apache.org%3E]:
Do not use {{SlingRepositoryInitializer}} for repoinit at all. Instead we
should support components to better handle absence of users, paths and ACLs
([Creating a service user for your own
bundle|https://lists.apache.org/thread.html/c88a36eb4684fd162174ea8b979f07552ff6ed4695035aef561a52dc@%3Cusers.sling.apache.org%3E]).
> Dependency problem between RepositoryInitializer and
> AbstractSlingRepositoryManager
> -----------------------------------------------------------------------------------
>
> Key: SLING-6263
> URL: https://issues.apache.org/jira/browse/SLING-6263
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Carsten Ziegeler
> Priority: Blocker
> Fix For: JCR Base 2.4.2
>
>
> As we can currently see on our Jenkins:
> https://builds.apache.org/job/sling-launchpad-builder-1.8/lastSuccessfulBuild/artifact/target/_-32861/sling/logs/error.log
> there is a dependency problem with the repository and repoinit.
> When the repository is started, there is no RepositoryInitializer
> service and the repository starts up fine. When the
> RepositoryInitializer arrives later it is completely ignored.
> I'm not 100% sure how to fix this, easiest fix would be to make a
> RepositoryInitializer required, but then this would mean only one of
> them is required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
