CMS Dependency Upgrade

Use Packaged CMS Dependencies

In your project's cms module, remove these "product dependencies"

<dependency>
  <groupId>org.onehippo.cms7.hst.dependencies</groupId>
  <artifactId>hst-repository-dependencies</artifactId>
  <type>pom</type>
</dependency>
<dependency>
  <groupId>org.onehippo.cms7.hst.dependencies</groupId>
  <artifactId>hst-cms-dependencies</artifactId>
  <type>pom</type>
</dependency>
<dependency>
  <groupId>org.onehippo.cms7</groupId>
  <artifactId>hippo-addon-channel-manager-frontend</artifactId>
</dependency>
<dependency>
  <groupId>org.onehippo.cms7</groupId>
  <artifactId>hippo-addon-channel-manager-repository</artifactId>
</dependency>

add hst-addon-hcm-site dependency:

<dependency>
  <groupId>org.onehippo.cms7.hst.toolkit-resources.addon</groupId>
  <artifactId>hst-addon-hcm-site</artifactId>
</dependency>

and ensure that below "dependency package" is present:

<dependency>
  <groupId>org.onehippo.cms7</groupId>
  <artifactId>hippo-package-cms-dependencies</artifactId>
  <type>pom</type>
</dependency>

In the rare case that your project excludes the Channel Manager from the CMS web application, annotate this dependency package as follows:

<dependency>
  <groupId>org.onehippo.cms7</groupId>
  <artifactId>hippo-package-cms-dependencies</artifactId>
  <type>pom</type>
  <exclusions>
    <exclusion>
      <groupId>org.onehippo.cms7</groupId>
      <artifactId>hippo-addon-channel-manager-frontend</artifactId>
    </exclusion>
    <exclusion>
      <groupId>org.onehippo.cms7</groupId>
      <artifactId>hippo-addon-channel-manager-repository</artifactId>
    </exclusion>
  </exclusions>
</dependency>

Rename Packaged Enterprise CMS Dependencies

If your project is an enterprise project, i.e. the parent artifact of your project's root artifact is hippo-cms7-enterprise-release, the cms module contains a dependency on the artifact hippo-enterprise-package-app-dependencies. Rename this artifact to hippo-enterprise-package-cms-dependencies.

Add Shared HST-API Artifact to Distribution

Prior to version 13, the hst-api artifact used to be a dependency of the CMS. As of version 13, this artifact must live in the shared library, so both the CMS and the site web application(s) can access it.

In order to make hst-api available in a local development environment, the cargo.run Maven profile has been updated in the product code, and no project-specific change is necessary. However, in order to package hst-api correctly in the distribution produced by your project (mvn -Pdist), you must adjust your project's configuration of the Maven assembly plugin to output hst-api into the shared libraries directory. Typically this means that you must add hst-api to the <includes> in src/main/assembly/shared-lib-component.xml:

<include>org.onehippo.cms7.hst:hst-api</include>