Return-Path: 
 <axis-dev-return-26310-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 61299 invoked from network); 11 Dec 2003 16:19:38 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 11 Dec 2003 16:19:38 -0000
Received: (qmail 15333 invoked by uid 500); 11 Dec 2003 16:19:29 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 15307 invoked by uid 500); 11 Dec 2003 16:19:29 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-dev@ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 15296 invoked from network); 11 Dec 2003 16:19:29 -0000
Date: Thu, 11 Dec 2003 08:19:34 -0800 (PST)
From: Vidyanand Murunikkara <vidyanand@apache.org>
To: axis-dev@ws.apache.org
Subject: Re:Bug in ANT-Script in CVS? (fwd)
Message-ID: <20031211081853.A60638@minotaur.apache.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: localhost 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N


Try putting junit.jar in ant's lib directory.

> -----Original Message-----
> From: Harald Pollak [mailto:h.pollak@pke.at]
> Sent: Thursday, December 11, 2003 9:24 AM
> To: Axis-Dev
> Subject: Bug in ANT-Script in CVS?
>
>
> I have checked out Axis from CVS
>
> I have following jars in lib dir from java folder:
>
> activation.jar
> mail.jar
> commons-discovery.jar
> javax.servlet.jar
> wsdl4j.jar
> junit.jar
> commons-logging.jar
> log4j-1.2.8.jar
>
>
> following message commes and building stops:
>
> junit:
>
> junit:
>
> BUILD FAILED
> file:/home/hpollak/apache-cvs/ws-axis/java/buildTest.xml:107: 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.
>
> Total time: 1 minute 19 seconds
>
>
> if I make those changes in buildTest.xml distribution is build:
>
> <!-- =================================================================== -->
>   <!-- Compiles the JUnit testcases -->
>   <!-- =================================================================== -->
>
>   <!-- =================================================================== -->
>   <!-- Runs the JUnit package testcases -->
>   <!-- =================================================================== -->
>   <target name="junit" if="junit.present">
>   </target>
> <!--
>   <target name="junit" if="junit.present">
>     <junit printsummary="yes" haltonfailure="${test.functional.fail}" fork="yes">
>       <classpath refid="classpath" />
>       <formatter type="xml" />
>       <batchtest todir="${test.functional.reportdir}">
>         <fileset dir="${build.dir}/classes" excludesfile="${axis.home}/junit-exclude-tests.txt">
> -->
>           <!-- Convention: each package that's being tested
>                 has its own test class collecting all the tests -->
> <!--
>   <include name="**/PackageTests.class" />
> -->
> <!-- <include name="**/test/*TestSuite.class"/> -->
> <!--        </fileset>
>       </batchtest>
>     </junit>
>   </target>
> -->
>   <!-- =================================================================== -->
>   <!-- Functional tests, no server (for testing under debugger)            -->
>   <!-- =================================================================== -->
>
>
> any idea? is it a bug in the build file?
> Harry?
>
>