Carsten Ziegeler created SLING-6263:
---------------------------------------
Summary: 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)
