Hi Henning,
On Sun, 7 Aug 2005, Henning P. Schmiedehausen wrote:
bad news: It still fails (though in a new and exciting way) if you run
the tests like this:
% maven -Dmaven.test.skip=true -Dtorque.testProfile=profile/henning.profile
runtime:test
[...]
BUILD FAILED
File...... /home/henning/scratch/torque-svn/db-torque/maven.xml
Element... ant
Line...... 130
Column.... 29
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:
[...]
The runtime test seems to rely on maven to create the junit tasks for
ant. So when you skip the tests, the junit task is not defined and the
runtime test fails. It should run independently from the maven driven
unit tests.
This is a problem with the classpath maven sets in the maven shell script
and the ant classloaders. Read
http://ant.apache.org/faq.html#delegating-classloader
and look at the -classpath definition in the java command in the maven
shell script.
To resolve the issue, you can either edit the maven shell script to
include junit.jar in the classpath, or you can copy junit-3.8.1.jar into
the $MAVEN_HOME/lib/endorsed directory.
Don't ask me why it works if you do not set -Dmaven.test.skip=true
Of course this could also be a problem with the ant installation from
jpackage. I know that Stefan Bodewig almost gets a fit every time I
mention "ant and jpackage" or "ant and Redhat". ;-)
This is not the problem. I have installed ant from scratch and can
reproduce the problem.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
