Dion Gillard wrote:
I don't think that'll work. I believe the solution is something along the lines of the following:Set the user.home system property in the child subproject?
On Fri, 09 Jul 2004 23:38:58 -0400, Omair-Inam Abdul-Matin <[EMAIL PROTECTED]> wrote:
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]
<goal name="printenv-test-all">
<echo>----- MASTER PROJECT ENV -----</echo>
<attainGoal name="printenv"/>
<!-- only collect the project names -->
<m:reactor basedir="${basedir}"
includes="*/project.xml"
goals="printenv"
banner="Building"
collectOnly="false"
postProcessing="true"
ignoreFailures="false"
/>
<j:forEach var="reactorProject" items="${reactorProjects}">
<!-- set the basedir value here for each project and then
attain the desired goal -->
</j:forEach>
</goal>I was surprised why the reactor doc doesn't mention the fact that any instance var of the Project class can be accessed (e.g. ${reactorProject.groupId}) I had to actually go thru the source and then find the instance vars.
Omair
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
