This project provides extra Folder Context Menu items such as 'Copy folder...' and 'Move folder...' for BloomReach XM with extensible base implementations for developers.
The documentation can generated locally by this command:
mvn clean site
The output is in the target/site/ directory by default. You can open target/site/index.html in a browser.
Releases are fully automated via GitHub Actions. No local version bumping or tagging required.
- Merge
developintomaster - Go to Actions → Release → Run workflow (from
master) - Enter the release version (e.g.
5.2.1) and the next SNAPSHOT (e.g.5.2.2-SNAPSHOT) - Click Run workflow
The Release workflow will:
- Set the version in
pom.xmlanddemo/pom.xmlto the release version - Build and test the project and demo
- Deploy the artifact to the Bloomreach Forge Maven repository
- Generate
forge-addon.yamlfrom.forge/addon-config.yaml - Commit the release files (
pom.xml+forge-addon.yaml) tomasterand create thex.y.ztag — the tag points to this commit, soforge-addon.yamlis readable via the GitHub Contents API at that ref - Create a GitHub Release with
forge-addon.yamlalso attached as a downloadable asset - Bump
pom.xmlanddemo/pom.xmlto 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 | Purpose |
|---|---|
develop |
Active development |
master |
Release branch — the release workflow runs here |
gh-pages |
Published documentation (managed by CI, do not edit manually) |