commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r161697 - jakarta/commons/proper/lang/trunk/xdocs/developerguide.xml
Date Sun, 17 Apr 2005 21:27:37 GMT
Author: stevencaswell
Date: Sun Apr 17 14:27:36 2005
New Revision: 161697

added section on building with initial description of setting up clover license for site generation


Modified: jakarta/commons/proper/lang/trunk/xdocs/developerguide.xml
--- jakarta/commons/proper/lang/trunk/xdocs/developerguide.xml (original)
+++ jakarta/commons/proper/lang/trunk/xdocs/developerguide.xml Sun Apr 17 14:27:36 2005
@@ -31,6 +31,7 @@
 <a href="#PackageStructure">[Package Structure]</a>
 <a href="#UtilityClasses">[Utility Classes]</a>
 <a href="#Javadoc">[Javadoc]</a>
+<a href="#Building">[Building]</a>
 <br /><br />
@@ -135,6 +136,21 @@
 However, it's not something to get worked up about.
 Lots of spelling differences will creep in all over.</p>
+<a name="Building"></a>
+<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:
+<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 <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
+name should be <b>clover-1.3.2.license</b>.</li>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message