Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-6263

Dependency problem between RepositoryInitializer and AbstractSlingRepositoryManager

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: JCR Base 2.4.2
    • Component/s: JCR
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              cziegeler Carsten Ziegeler
              Reporter:
              cziegeler Carsten Ziegeler
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: