This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new dad8365 Point to the corresponding source code modules (we should do
that more often)
dad8365 is described below
commit dad836507c64c02727181be0978beadc9cf8d7a1
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Thu Feb 6 16:12:52 2020 +0100
Point to the corresponding source code modules (we should do that more
often)
---
.../jbake/content/documentation/bundles/repository-initialization.md | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/src/main/jbake/content/documentation/bundles/repository-initialization.md
b/src/main/jbake/content/documentation/bundles/repository-initialization.md
index d7cfa6c..d734489 100644
--- a/src/main/jbake/content/documentation/bundles/repository-initialization.md
+++ b/src/main/jbake/content/documentation/bundles/repository-initialization.md
@@ -28,6 +28,9 @@ If any of them throws an Exception, the `SlingRepository`
service is not registe
The `org.apache.sling.repoinit.parser` implements a mini-language meant to
create paths, service users and Access Control Lists in a content repository,
as
well as registering JCR namespaces and node types.
+As I write this, the source code consists of [three
modules](https://github.com/apache?utf8=%E2%9C%93&q=sling+repoinit): the
parser, the JCR
+repoinit adapter module and the integration tests.
+
The language grammar is defined (using the JavaCC compiler-compiler, which has
no runtime dependencies) in the `RepoInitGrammar.jjt` file in that module, and
the automated tests provide a number of [test
cases](https://github.com/apache/sling-org-apache-sling-repoinit-parser/tree/master/src/test/resources/testcases)
which demonstrate various features.
The companion `org.apache.sling.jcr.repoinit` module implements those
operations on an Oak JCR repository, using a `SlingRepositoryInitializer`
