Setting the right dependencies in your POM

Today it is common usage to specify the version dependency between a Forge component and the CMS/HST version without a range, for example: <version>2.06.06</version>

However what we want is to be independent of the minor version, otherwise the Forge component is unusable with every new tag of CMS/HST. The Hippo product services team will keep CMS and HST backward compatible if only the minor version number changes (minor version means zz in xx.yy.zz).

You should specify in the pom of your Forge component:

CMS dependency: <version>[2.07.00,2.08.00)</version>
HST dependency: <version>[2.03.09,2.04.00)</version>

The scope must be set to 'provided'.

When updating your Forge plug-in make sure the categories are also specified correctly.