Commit 9996e932 authored by Ate Douma's avatar Ate Douma

TRIVIAL cleanup master

parent 603dd2c2

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

This diff is collapsed.
Hippo Site Toolkit
Copyright 2008-2018 Hippo B.V. (
This product includes software developed by:
Hippo B.V., Amsterdam, The Netherlands (;
The Apache Software Foundation (
NOTICE: Only our own original work is licensed under the terms of the
Apache License Version 2.0. The licenses of some libraries might impose
different redistribution or general licensing terms than those stated in the
Apache License. Users and redistributors are hereby requested to verify these
conditions and agree upon them.
How to test and build Hippo Site Toolkit
Very brief introduction to how to build, test and run the Hippo Site Toolkit!
* Java 8
* Maven 3 (3.2.1+)
* [Optional] Tomcat 8.0.x if you want to deploy and run on Tomcat.)
1. Build with testing
mvn clean install
2. Build with skipping tests
mvn clean install -DskipTests
3. Build with Hippo Snapshot Repository Flag
- Note: Mostly you do not need this when you check out and build a released version!
Needed only when you build the TRUNK having snapshot dependencies!
- Note: Please beware that the '-Dhippo.snapshots' option is effective only when you define
a Maven profile with this property in your settings.xml for the Hippo snapshot repository.
For details, see
- Add '-Dhippo.snapshots' for snapshot dependencies.
For example,
$ mvn clean install -Dhippo.snapshots -DskipTests
Creating the mvn site with javadocs: type from the root
mvn site
All aggregated javadocs are generated in target/site/apidocs and all aggregated test javadocs are generated in target/site/testapidocs.
In addition, "The User API JavaDocs", which includes only api, mock, commons, content-beans and client, are generated in target/site/userapidocs/ separately.
Also, a menu link item for "The User API JavaDocs" has been added in site.xml.
mvn site:stage
If you want to see sub-module links in your generated site, also see
\ No newline at end of file
# This is not the branch you're looking for...
BloomReach only provides the git trees for the release tags of Hippo CMS, as explained on
To checkout the code for a specific release tag, after cloning this repository, use the following:
## to show the available tags
git tag
## to checkout a specific tag
git checkout <tag name>
## to modify a project
If you want to make modifications to a project, for example to create a patch, create a new fork branch from the specific tag like this:
git checkout -b forked-<tag name> <tag name>
For the latter, also see the **Build from Source** documentation at
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8"?>
Copyright 2008-2016 Hippo B.V. (
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS"
See the License for the specific language governing permissions and
limitations under the License. -->
<project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
<name>Hippo Site Toolkit API</name>
<description>Hippo Site Toolkit Api</description>
<!-- Test dependencies -->
<!-- To exclude commons-collections depedency explicitly.
hst-commons must not have this dependency because it is deployed to shared lib directory. -->
* Copyright 2012-2013 Hippo B.V. (
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.