SLING-12459 - Redirect sonarcloud notifications to commits@apache.sling.org
1 file changed
tree: 060bc5bca9a5bf1996a29f1112bc59826c8e964b
  1. src/
  2. .asf.yaml
  3. .git-blame-ignore-revs
  4. .gitignore
  5. .sling-module.json
  6. bnd.bnd
  7. CODE_OF_CONDUCT.md
  8. CONTRIBUTING.md
  9. Jenkinsfile
  10. LICENSE
  11. pom.xml
  12. README.md
README.md

Apache Sling

Build Status Test Status Coverage Sonarcloud Status JavaDoc Maven Central jcr License

Apache Sling JCR RepoInit module

This module is part of the Apache Sling project.

This module implements Repository Initalization operations for the Sling repoinit modules, operations that can initialize content, service users and privileges in a JCR content repository.

The user documentation for the Sling Repoinit modules is at https://sling.apache.org/documentation/bundles/repository-initialization.html

Updating to a newer version of Jackrabbit Oak

The Oak version (and the associated Jackrabbit version) must be maintained in two locations:

  • pom.xml for build and unit testing
  • src/test/features for integration testing

Since the integration tests rely on the Sling Starter to provide the the base instance values, it happens that the Oak version used by repoinit is more recent than the one provided in the starter.

We should not depend on SNAPSHOT starter versions, since this bundle is released more often than the Starter. Therefore the recommended approach is to override the needed bundles in the following manner:

  • in src/test/provisioning/sling.txt - all bundles from the Sling Starter part of the ‘sling.txt’ feature
  • in src/test/provisioning/oak.txt - all bundles from the Sling Starter part of the ‘oak.txt’ feature

For a more concrete example, see SLING-8627 - Update sling-jcr-repoinit to Oak 1.16.0 and Jackrabbit 2.18 and associated commits.