From fbeb0dbd3d7543f0241bd318b0bb38c5c31b4f1a Mon Sep 17 00:00:00 2001
From: Steven Caswell <stevencaswell@apache.org>
Date: Sun, 17 Apr 2005 21:27:36 +0000
Subject: [PATCH] added section on building with initial description of setting
 up clover license for site generation

git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/lang/trunk@161697 13f79535-47bb-0310-9956-ffa450edef68
---
 xdocs/developerguide.xml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/xdocs/developerguide.xml b/xdocs/developerguide.xml
index cb28edd2c..0b28cd3a4 100644
--- a/xdocs/developerguide.xml
+++ b/xdocs/developerguide.xml
@@ -31,6 +31,7 @@ $Id$<br />
 <a href="#PackageStructure">[Package Structure]</a>
 <a href="#UtilityClasses">[Utility Classes]</a>
 <a href="#Javadoc">[Javadoc]</a>
+<a href="#Building">[Building]</a>
 <br /><br />
 </div>
 
@@ -135,6 +136,21 @@ To avoid misplaced jeers of 'americanisation', the people making this decision l
 However, it's not something to get worked up about.
 Lots of spelling differences will creep in all over.</p>
 
+<a name="Building"></a>
+<h3>5.BUILDING</h3>
+<h4>Site Generation</h4>
+<p>Site generation via maven includes Clover report generation. Since Clover
+requires a license, the proper license file must be placed where the maven
+Clover plugin can find it. This can be done as follows:
+<ul>
+<li>Obtain the license file from the committers svn repository (clover.license)</li>
+<li>Copy clover.license to the lang base directory (the top level directory where project.xml, maven.xml, etc. reside).</li>
+<li>Copy clover.license to your maven repository Clover licenses directory, named clover-[version].license, where [version] is the version specified in the
+project.properties <b>maven.jar.clover</b> property. For example, if
+<b>maven.jar.clover</b> is set to <b>1.3.2</b>, then the clover license file
+name should be <b>clover-1.3.2.license</b>.</li>
+</ul>
+</p>
 </section>
 </body>
 </document>