On 9/20/06, Ivan Volosyuk <[EMAIL PROTECTED]> wrote:

Hi All,

I have some kind of configuration problem. DRLVM's 'build test' fails
on my machine on kernel tests with attached message. As I can see
junit.jar is added in CLASSPATH in build.sh script, but something not
work as expected. '-Djuint.home=make/tmp' or
'-Djunit.jar=make/tmp/junit.jar' doesn't help either. What is the
hidden knowledge how to run the tests?


Try to indicate an absolute path to the jar file. I want to hope all should
work for this case.
Please, let know me if it helps.

Thanks,
Vladimir.

--
Ivan


--- build.sh test output -----------------------------------------------
kernel.test:

-run-kernel-test:
    [echo]
    [echo]             ==================================
    [echo]             Run kernel tests using jitrino.jet
    [echo]             ==================================
    [echo]
   [mkdir] Created dir:

/home/ivan/svn/drlvm/trunk/build/lnx_ia32_gcc_debug/semis/kernel.tests/reports/jitrino.jet
    [echo] RUNNING : java.lang.Class1_5Test

BUILD FAILED
/home/ivan/svn/drlvm/trunk/build/make/build.xml:373: The following
error occurred while executing this line:
/home/ivan/svn/drlvm/trunk/build/make/build_component.xml:72: The
following error occurred while executing this line:

/home/ivan/svn/drlvm/trunk/build/lnx_ia32_gcc_debug/semis/build/targets/kernel.test.xml:149:
The following error occurred while executing this line:

/home/ivan/svn/drlvm/trunk/build/lnx_ia32_gcc_debug/semis/build/targets/kernel.test.xml:161:
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 the JAR file and/or libraries
    implementing the functionality were not found at the time you
    yourself built your installation of Ant from the Ant sources.
  Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
    task and make sure it contains more than merely a
META-INF/MANIFEST.MF.
    If all it contains is the manifest, then rebuild Ant with the needed
    libraries present in ${ant.home}/lib/optional/ , or alternatively,
    download a pre-built 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>.
- You are attempting to use a task defined using
   <presetdef> or <macrodef> but have spelt wrong or not
  defined it at the point of use

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.

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to