You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by "Verma, Nitin (GECP, OTHER, 529706)" <NI...@APPL.GE.COM> on 2003/05/27 09:24:27 UTC

JUNIT task not running

run:

BUILD FAILED
file:E:/projects/ts/serverconfig/serverconfig/build.xml:147: Could not
create task or type of type: junit.

Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
 - You have misspelt 'junit'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
   and this is not found at the right place in the classpath.
   Fix: check the documentation for dependencies.
   Fix: declare the task.
 - The task is an Ant optional task and optional.jar is absent
   Fix: look for optional.jar in ANT_HOME/lib, download if needed
 - The task was not built into optional.jar as dependent
   libraries were not found at build time.
   Fix: look in the JAR to verify, then rebuild with the needed
   libraries, or download a release version from apache.org
 - The build file was written for a later version of Ant
   Fix: upgrade to at least the latest release version of Ant
 - The task is not an Ant core or optional task
   and needs to be declared using <taskdef>.

Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath

Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.

RE: JUNIT task not running

Posted by Adam Jack <aj...@TrySybase.com>.
JUNIT task not runningYou clearly didn't read this message that you posted:
    Please neither file bug reports on this problem, nor email the
    Ant mailing lists, until all of these causes have been explored,
    as this is not an Ant bug.

I assume you've not installed junit, http://www.junit.org, or add it to the
classpath or ...

Adam

  -----Original Message-----
  From: Verma, Nitin (GECP, OTHER, 529706) [mailto:NITIN.VERMA@APPL.GE.COM]
  Sent: Tuesday, May 27, 2003 1:24 AM
  To: Ant Users List
  Subject: JUNIT task not running


  run:

  BUILD FAILED
  file:E:/projects/ts/serverconfig/serverconfig/build.xml:147: Could not
create task or type of type: junit.

  Ant could not find the task or a class this task relies upon.

  This is common and has a number of causes; the usual
  solutions are to read the manual pages then download and
  install needed JAR files, or fix the build file:
   - You have misspelt 'junit'.
     Fix: check your spelling.
   - The task needs an external JAR file to execute
     and this is not found at the right place in the classpath.
     Fix: check the documentation for dependencies.
     Fix: declare the task.
   - The task is an Ant optional task and optional.jar is absent
     Fix: look for optional.jar in ANT_HOME/lib, download if needed
   - The task was not built into optional.jar as dependent
     libraries were not found at build time.
     Fix: look in the JAR to verify, then rebuild with the needed
     libraries, or download a release version from apache.org
   - The build file was written for a later version of Ant
     Fix: upgrade to at least the latest release version of Ant
   - The task is not an Ant core or optional task
     and needs to be declared using <taskdef>.

  Remember that for JAR files to be visible to Ant tasks implemented
  in ANT_HOME/lib, the files must be in the same directory or on the
  classpath

  Please neither file bug reports on this problem, nor email the
  Ant mailing lists, until all of these causes have been explored,
  as this is not an Ant bug.

Re: JUNIT task not running

Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
Ummmm......

On Tuesday, May 27, 2003, at 03:24  AM, Verma, Nitin (GECP, OTHER, 
529706) wrote:
> Please neither file bug reports on this problem, nor email the
> Ant mailing lists, until all of these causes have been explored,
> as this is not an Ant bug.
>

:))