Solved the problem,
I discovered a missing jar-file.
Sorry for the spam...
Dominik
+---------------------------------------------------------------------+
_/_/_/_/_/ _/_/_/ __/_/_/_/ Dominik Dahlem
_/ _/ _/ _/ _/ M.Sc. student, Computer Science
_/ _/ _/ _/ Trinity College Dublin
_/ _/ _/ _/ tel : +353 (0)1 608
_/ _/ _/ _/ _/ email: [EMAIL PROTECTED]
_/ _/_/_/ __/_/_/_/ www : http://www.cs.tcd.ie/~dahlemd
+---------------------------------------------------------------------+
-----Original Message-----
From: Dominik Dahlem [mailto:[EMAIL PROTECTED]
Sent: 14 July 2003 18:01
To: [EMAIL PROTECTED]
Subject: JUnit forking problem
Hi all,
I have a problem running a test with the property maven.junit.fork=yes.
In default mode, this test runs fine. I ran the "maven test -X" to check
the classpath with no result. Both classpaths (fork=yes/no) contain the
jar files needed to run the test.
Is there any issue? Am I missing something?
Thx,
Dominik
+---------------------------------------------------------------------+
_/_/_/_/_/ _/_/_/ __/_/_/_/ Dominik Dahlem
_/ _/ _/ _/ _/ M.Sc. student, Computer Science
_/ _/ _/ _/ Trinity College Dublin
_/ _/ _/ _/ tel : +353 (0)1 608
_/ _/ _/ _/ _/ email: [EMAIL PROTECTED]
_/ _/_/_/ __/_/_/_/ www : http://www.cs.tcd.ie/~dahlemd
+---------------------------------------------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
