From 49f1578e9ed7b2f5b5b48e8f488dfbb6300fc907 Mon Sep 17 00:00:00 2001
From: Henri Yandell
Date: Fri, 4 Aug 2006 06:49:04 +0000
Subject: [PATCH] Removed clover bits that were left over from the switch to
cobertura
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/lang/trunk@428648 13f79535-47bb-0310-9956-ffa450edef68
---
project.properties | 4 ----
xdocs/developerguide.xml | 13 -------------
2 files changed, 17 deletions(-)
diff --git a/project.properties b/project.properties
index 8e210854d..193729277 100644
--- a/project.properties
+++ b/project.properties
@@ -56,7 +56,3 @@ maven.compile.target = 1.1
# Corresponds to the source attribute for the ant javac task.
# Valid values are 1.3, 1.4, 1.5.
maven.compile.source = 1.3
-
-maven.jar.override=on
-maven.jar.clover=1.3.2
-maven.clover.license.path=clover.license
diff --git a/xdocs/developerguide.xml b/xdocs/developerguide.xml
index d99dd438b..64f946554 100644
--- a/xdocs/developerguide.xml
+++ b/xdocs/developerguide.xml
@@ -138,19 +138,6 @@ Lots of spelling differences will creep in all over.
5.BUILDING
-Site Generation
-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:
-
-- Obtain the license file (clover.license) from the committers svn repository (https://svn.apache.org/repos/private/committers/), in the donated-licenses path.
-- Copy clover.license to the lang base directory (the top level directory where project.xml, maven.xml, etc. reside).
-- Copy clover.license to your maven repository Clover licenses directory, named clover-[version].license, where [version] is the version specified in the
-project.properties maven.jar.clover property. For example, if
-maven.jar.clover is set to 1.3.2, then the clover license file
-name should be clover-1.3.2.license.
-
-
Building a Release
Commons Lang is intented to interoperate with Java version 1.2 and higher. To