Fixed issue with Clover task and type definitions not using an explicit classpath which apparently breaks under Maven 1.1.

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@169507 13f79535-47bb-0310-9956-ffa450edef68

clover/plugin.jelly

@@ -49,8 +49,8 @@
       </j:choose>
     </ant:path>
 
-    <ant:taskdef resource="clovertasks"/>
-    <ant:typedef resource="clovertypes"/>
+    <ant:taskdef resource="clovertasks" classpathref="clover.classpath"/>
+    <ant:typedef resource="clovertypes" classpathref="clover.classpath"/>
 
     <!-- Check for the deprecated maven.clover.database.dir property -->
     <j:choose>

clover/xdocs/changes.xml

@@ -26,6 +26,10 @@
   </properties>
   <body>
     <release version="1.9-SNAPSHOT" date="in SVN">
+      <action dev="vmassol" type="fix">
+        Fixed issue with Clover task and type definitions not using an
+        explicit classpath which apparently breaks under Maven 1.1.
+      </action>
       <action dev="vmassol" type="update" issue="MPCLOVER-35">
         Always generate Clover reports even when there is no coverage data. One
         of the reason is that Clover generates metrics other than coverage