Andy was right about the <unitTest> tags not being there.  Thanks for your help.  Now 
the unit tests run, but I can't get JCoverage or Clover to run?  I ran it twice, once 
with the Clover report and once with the JCoverage report.  The results are below and 
I attached the project.xml file with some of our project information taken out.  Also, 
the plugin section of the Maven website appears to not differentiate between plugins 
that are used for reports and other plugins.  Is there a list anywhere of all the 
plugins which are for reports?

Jay


C:\Eclipse\workspace\ERAWeb>maven site:generate
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-10

BUILD FAILED
File...... file:/C:/Documents and Settings/Owner/.maven/plugins/maven-xdoc-plugi
n-1.4-SNAPSHOT/
Element... attainGoal
Line...... 558
Column.... 48
No goal [maven-jcoverage-plugin:register]
Total time:  4 seconds


C:\Eclipse\workspace\ERAWeb>maven site:generate
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-10
site:
xdoc:register-reports:
maven-jdepend-plugin:register:
maven-pmd-plugin:register:
maven-clover-plugin:register:
maven-statcvs-plugin:register:
maven-changelog-plugin:register:
maven-changes-plugin:register:
maven-file-activity-plugin:register:
maven-developer-activity-plugin:register:
maven-javadoc-plugin:register:
maven-jxr-plugin:register:
maven-junit-report-plugin:register:
maven-tasklist-plugin:register:
maven-checkstyle-plugin:register:
maven-simian-plugin:register:

site:run-reports:
    [echo] Generating the Metrics...
maven-jdepend-plugin:report:
Overriding previous definition of reference to clover.classpath
java:prepare-filesystem:
java:compile:
    [echo] Compiling to C:\Eclipse\workspace\ERAWeb/target/classes

    [echo] Generating the PMD Report...
pmd:report:
    [echo] Running the PMD task with C:\Documents and Settings\Owner\.maven\plug
ins\maven-pmd-plugin-1.1-SNAPSHOT\plugin-resources/rulesets/basic.xml,C:\Documen
ts and Settings\Owner\.maven\plugins\maven-pmd-plugin-1.1-SNAPSHOT\plugin-resour
ces/rulesets/unusedcode.xml,C:\Documents and Settings\Owner\.maven\plugins\maven
-pmd-plugin-1.1-SNAPSHOT\plugin-resources/rulesets/imports.xml ...
    [echo] Converting the PMD report to xdoc ...
    [echo] Generating the Clover...
BUILD FAILED
File...... file:/C:/Documents and Settings/Owner/.maven/plugins/maven-clover-plu
gin-1.2-SNAPSHOT/
Element... ant:taskdef
Line...... 60
Column.... 39
(class: com/cortexeb/tools/clover/tasks/HistoryPoint, method: execute signature:
 ()V) Incompatible argument to function
Total time:  47 seconds


-----Original Message----- 
From: Andy Jefferson [mailto:[EMAIL PROTECTED] 
Sent: Thu 9/25/2003 2:07 PM 
To: Maven Users List 
Cc: 
Subject: Re: JUnit Tests


On Thursday 25 Sep 2003 19:34, Askren, Jay wrote:
> I am running Maven beta 10 and I cant seem to get the J-Unit tests plugin
> to work to work. Im running Maven on Windows XP with  Java 1.41_02-b06. 
> Here is the output from Maven before it dies:

> BUILD FAILED
> File...... file:/C:/Documents and
> Settings/Owner/.maven/plugins/maven-test-plugi n-1.3/
> Element... resources:copy
> Line...... 299
> Column.... 11
> java.lang.NullPointerException
> Total time: 3 minutes 7 seconds
>
>
> Does anyone have any idea what I need to do to get this to work?

 

Have you specified the part of the project.xml something like the following
...

<build>
<unitTestSourceDirectory>'your test dir'</unitTestSourceDirectory>
<unitTest>
</unitTest>
</build>

i.e have you included the <unitTest></unitTest> part ... I seem to remember it
is sensitive to that being missing. If in doubt, post your project.xml to the
list so people can help


--
Andy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to