Patched Jackrabbit in Bloomreach Content Repository

Bloomreach Content uses Apache Jackrabbit 2.x as the foundation for its content repository and persistence layer. The product includes a patched version of Jackrabbit to address issues and requirements that cannot be met by the official releases.

Whenever possible, Bloomreach contributes improvements back to the Jackrabbit project. However, there are situations where immediate fixes or Bloomreach-specific enhancements are required. These cases may include unresolved bugs or features that are unique to Bloomreach Content and not yet available in Jackrabbit.

To manage these changes, Bloomreach maintains a bloomreach/jackrabbit Git mirror of the official Apache Jackrabbit repository (git://git.apache.org/jackrabbit.git). This mirror is automatically synchronized with the upstream Apache repository.

Patched versions are managed in dedicated branches named bloomreach/jackrabbit-<version>-hx, where <version> refers to the Jackrabbit release and -hx indicates the initial patch set for that version. All new patches for a given version are developed in this branch. When a patched release is ready, it is tagged as jackrabbit-<version>-hx. Additional patches for the same version are added to the same branch, and subsequent patched releases are tagged as -hx+1, -hx+2, and so on.

If an existing patch set for a specific Jackrabbit version needs to be modified, a new branch is created. This branch is named bloomreach/jackrabbit-<version>-hy, based on the previous -hx branch up to the patch that requires changes. Further modifications are made in this new branch.

When upgrading to a new Jackrabbit version, Bloomreach starts from the base Jackrabbit release tag. Existing patches are reapplied and adjusted as needed in a new bloomreach/jackrabbit-<new version>-h1 branch.

This approach allows Bloomreach to deliver required fixes and enhancements while maintaining alignment with the upstream Jackrabbit project.