[
https://issues.apache.org/jira/browse/SLING-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654719#comment-15654719
]
Carsten Ziegeler commented on SLING-6263:
-----------------------------------------
Ok, I guess I have missed parts of that discussion somehow.
I see your point, what about (and we should maybe discuss this on the mailing
list or in another issue) if we add a service registration property to
SlingRepositoryInitializer. It defaults to "execute me whenever I'm there" (or
maybe better wording) and it can be changed to "only execute my before
repositoy start".
This would solve your problem, without creating a new interface and would not
change what we have now.
> 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
> Assignee: 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)
