axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harald Pollak <h.pol...@pke.at>
Subject Bug in ANT-Script in CVS?
Date Thu, 11 Dec 2003 14:23:51 GMT
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?

Mime
View raw message