Introduction To Initializing The Repository

At each startup of a repository preconfigured initialization actions are performed if they were not performed before. The initialization actions are configured in files named src/main/resources/hippoecm-extension.xml. Each of the modules used by your CMS module may have such a file. All initialization actions from all these files are performed. Your CMS module is the module that has the war overlay on the hippo-package-cms-resources war. Good practice is that this is the module called 'cms'. It may also be your main project itself. Check the poms for <overlay> to find out.

If you do not have a hippoecm-extension.xml file yet, follow the good practice of using a separate 'content' module that only contains a pom.xml and the folder src/main/resources/. This folder should only contain the hippoecm-extension.xml file and all the CND and XML node files that are to be imported on initialization.

You CMS module should use this module, i.e. be dependent on it. Add a dependency entry to its pom.xml, e.g.: 

    <dependency>
       <groupId>org.onehippo.ecm.hst.demosuite</groupId>
       <artifactId>hst-demosuite-content</artifactId>
       <version>${project.version}</version>
       <type>jar</type>
    </dependency>

This is taken from the HST demosuite. Change the groupId and the artifactId. The variable ${pom.version} can be used when the version of the content module is the same as that of the CMS module, which is advisable.

Read more on this introduction... 

	Import CND File	How to automatically import a CND file during initialization of the repository?
	Import A Node XML File	How to automatically import a node XML file during initialization of the repository?
	Setting A Single Property	How to set a single property value in existing configuration.
	Enhanced XML File Import	How to control merging and overriding content from XML file using an enhanced XML file format.
	Content Delete	Upgrading when you use hippo:contentdelete in your hippoecm-extension.xml