commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r428648 - in /jakarta/commons/proper/lang/trunk: xdocs/developerguide.xml
Date Fri, 04 Aug 2006 06:49:04 GMT
Author: bayard
Date: Thu Aug  3 23:49:04 2006
New Revision: 428648

Removed clover bits that were left over from the switch to cobertura


Modified: jakarta/commons/proper/lang/trunk/
--- jakarta/commons/proper/lang/trunk/ (original)
+++ jakarta/commons/proper/lang/trunk/ Thu Aug  3 23:49:04 2006
@@ -56,7 +56,3 @@
 # Corresponds to the source attribute for the ant javac task. 
 # Valid values are 1.3, 1.4, 1.5. 
 maven.compile.source = 1.3

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 Thu Aug  3 23:49:04 2006
@@ -138,19 +138,6 @@
 <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 (clover.license) from the committers svn repository  (,
in the donated-licenses path.</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>
 <h4>Building a Release</h4>
 Commons Lang is intented to interoperate with Java version 1.2 and higher. To

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

View raw message