•  
Main
About Hippo Site Toolkit 1
Technical Documentation
Expression Language
Other

Building with Maven

Install Maven

Hippo Site Toolkit is built using Maven 2 (version 2.0.6 or newer). Follow the Maven installation instructions.

For Windows users
You need to take care that your local Maven 2 repository is not located in a folder with spaces in the pathname. The default Maven installation procedure will locate it in your home directory which on Windows is a subdirectory of the "Documents and Settings" directory. This means that you need to relocate your local Maven repository.

Create and edit the file c:\Documents and Settings\<Your Name>\.m2\settings.xml with the following content:

<settings xmlns="http://maven.apache.org/POM/4.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    <localRepository>C:\\mvnhome</localRepository>
</settings>

This effectively relocates your local Maven repository to c:\mvnhome.

Get the Hippo Site Toolkit sources

The source can be found at http://svn.hippocms.org/repos/hippo/hippo-site-toolkit/ and can be anonymously checked out using any Subversion client. Instructions on Subversion use can be found at http://svnbook.red-bean.com/. The following command checks out the trunk to a directory called 'hippo-site-toolkit':

~> svn co http://svn.hippocms.org/repos/hippo/hippo-site-toolkit/trunk hippo-site-toolkit
                

Build

Assuming that you have checked out the Hippo Site Toolkit sources in the directory ~/hippo-site-toolkit:

~> cd hippo-site-toolkit
~/hippo-site-toolkit> mvn install
                

This will take a while and put all project artifacts (jars, wars) in your local Maven repository.

Running the examples using Jetty

During development you can use Jetty to run the examples or your own Hippo Site Toolkit based web application.

~/hippo-site-toolkit> cd jsp-example-app
~/hippo-site-toolkit/jsp-example-app> mvn jetty:run
                

For production it is recommended to deploy your application as a WAR in a proper servlet container.