Upgrade Project Versions

Upgrade Parent Version

Change theversion of your project's parent artifact (eitherhippo-cms7-release orhippo-cms7-enterprise-release) to the most recent available version in the 14.x range.

With this change in place, you will have to go through a series of additional steps before your project is ready again to build and startup successfully. Most notably, by far the majority of the needed steps are with respect toupgrading the security configuration. Before completing that step, an earlier created project won't be able tobootstrap due toconfiguration errors.

Upgrade Essentials Version

Even thoughEssentials has been designed primarily to scaffold new projects, there may be reasons for hanging on to Essentials in your to-be-upgraded project. If so, change the<essentials.version> property in your project's rootpom.xml to the most recent available version in the 14.x range. If not, consider deleting theessentials module from your project.

Upgrade Dependency Versions

In the ideal case, all dependency versions are controlled - and upgraded - through the project's parent artifact, so you don't need to do anything. However, if your project contains version overrides of specific dependencies, investigate if these overrides are still applicable. Whenever possible, you should clean them up during the upgrade.

Your project may also contain dependencies on add-ons which are not managed through the project's parent artifact, such as community-supported Bloomreach Experience Manager add-ons from theBloomReach Forge. For such dependencies, it is very likely that your upgraded project will require a new version. If that version is already available, use it. If not, you can choose to ask the community to provide a 14-compatible version of the add-on, or to upgrade the add-on yourself.