Apache Camel - Hippo Events Support

Apache Camel - Hippo Events Support provides:

• A hippoevent: Apache Camel component
• A Camel Repository Scheduler Job component which can invoke a Camel Endpoint URI
• Utility classes to help integration between Hippo CMS/Repository and Apache Camel.

Documentation

Documentation is available at bloomreach-forge.github.io/camel-events-support

Docs are built automatically from the release tag and deployed to the gh-pages branch by the Deploy Docs workflow. They can also be triggered manually via workflow_dispatch.

To preview docs locally:

mvn clean site:site

The output will be in target/site/ and is ignored by Git.

Release Process

Releases are fully automated via GitHub Actions. No local version bumping or tagging required.

Steps

1. Merge develop into master
2. Go to Actions → Release → Run workflow (from master)
3. Enter the release version (e.g. 5.2.1) and the next SNAPSHOT (e.g. 5.2.2-SNAPSHOT)
4. Click Run workflow

The Release workflow will:

1. Set the version in pom.xml and demo/pom.xml to the release version
2. Build and test the project and demo
3. Deploy the artifact to the Bloomreach Forge Maven repository
4. Generate forge-addon.yaml from .forge/addon-config.yaml
5. Commit the release files (pom.xml + forge-addon.yaml) to master and create the x.y.z tag — the tag points to this commit, so forge-addon.yaml is readable via the GitHub Contents API at that ref
6. Create a GitHub Release with forge-addon.yaml also attached as a downloadable asset
7. Bump pom.xml and demo/pom.xml to the next SNAPSHOT and commit

Once the GitHub Release is published, the Deploy Docs workflow runs automatically and publishes the updated site to gh-pages.

The workflow also automatically pushes the next SNAPSHOT version to develop.

Branch model

Branch	Purpose
develop	Active development
master	Release branch — the release workflow runs here
gh-pages	Published documentation (managed by CI, do not edit manually)