Upgrade Project Versions

Upgrade Parent Version

Update the version of your project's parent artifact (hippo-cms7-release or hippo-cms7-enterprise-release) to the latest available version in the 14.x series.

After updating the parent version, you must complete additional upgrade steps before your project can build and start successfully. Most required changes involve upgrading the security configuration. Until you update the security configuration, the project will not bootstrap due to configuration errors.

Upgrade Essentials Version

Essentials is primarily intended for scaffolding new projects. If your project still uses Essentials, update the <essentials.version> property in the root pom.xml to the latest available 14.x version. If your project no longer requires Essentials, remove the essentials module from your project.

Upgrade Dependency Versions

Ideally, your project's parent artifact manages all dependency versions, and no further action is required. If your project overrides specific dependency versions, review each override to determine if it is still necessary. Remove unnecessary overrides during the upgrade process.

If your project depends on add-ons not managed by the parent artifact—such as community-supported Bloomreach Content add-ons from BloomReach Forge—verify compatibility with version 14.x. Use updated versions if available. If a compatible version does not exist, request an update from the community or update the add-on yourself.