Apache Jackrabbit Website

Clone this repo:
  1. 3ba2b81 Merge pull request #10 from apache/UPDATEINSTRUCTIONS by Julian Reschke · 2 weeks ago main
  2. a948cc4 JCR-5214: Release Jackrabbit 2.22.3 by Julian Reschke · 3 weeks ago
  3. ae446fd Release Apache Jackrabbit Oak 1.90.0 by Joerg Hoh · 4 weeks ago
  4. 0b0d9c6 JCR-5212: Release Jackrabbit 2.23.3-beta - site by Julian Reschke · 8 weeks ago
  5. 2301767 Apache Jackrabbit Board Report December 2025 (draft) by Marcel Reutegger · 8 weeks ago

Jackrabbit Site Generation

Apache License, Version 2.0, January 2004 Jenkins Status

This is the Git repository for the content of https://jackrabbit.apache.org/jcr/. Further information in website.

The Jackrabbit site lives as Markdown files in src/site/markdown such that it easy to view e.g. from GitHub. This project only generates the content below https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr, otherwise the scm-publish mechanism is too slow, checking out the entire site.

The Maven site plugin is used to build the web site as follows:

  1. In this project's directory execute:

    $ mvn site
    
  2. Review the site at target/site/index.html

  3. Commit and push your changes to the source files

Automatic Deployment

The main branch is automatically built on the ASF Jenkins after every commit and the results are automatically committed to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr from where the Website is being populated.

Manual Deployment

  1. Build and deploy the site to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr using:

    $ mvn site-deploy
    
  2. Finally review the site at https://jackrabbit.apache.org/jcr.

Note: To skip the final commit use -Dscmpublish.skipCheckin=true. You can then review all pending changes in target/scmpublish-checkout and follow up with svn commit manually.

Note: Every committer should be able to deploy the site. Deployment is done via svn commit to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr. The credentials are retrieved from a server with id apache.releases.https from the Maven Settings. Alternatively one can provide the credentials explicitly via -Dpassword and -Dusername (maven-scm-publish-plugin:publish-scm).