The easier solution is probably to set the JVM to fork for the Unit
Test. The JVM will then use the child project base dir as the working
folder instead of the master project base dir. 

Add:
maven.junit.fork=true 
In the project.properties of the child project causing problems.



-----Original Message-----
From: Omair-Inam Abdul-Matin [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 09, 2004 11:39 PM
To: [EMAIL PROTECTED]
Subject: Reactor: tests failing (working dir set to master proj dir not
child proj dir)

I'm using JUnit to run some regression tests that need to read in
configuration and data files.  For this it is necessary that the working
directory be the same as the project directory.  Recently the project
was subdivided into a master project and child subprojects.  Now when I
try to run unit tests by invoking the master build target, the tests
fail because apparently the working directory is the directory of the
master project not the current child project.  I believe this topic has
been brought up in a previous post but I was not able to find the
solution to the problem.

Can someone please nudge me in the correction direction?

Omair


---------------------------------------------------------------------
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]

Reply via email to