Hi Brett
Brett Porter (JIRA) wrote on Wednesday, November 23, 2005 3:08 AM:
>> When testing from the parent POM dir, all paths are relative to it.
>> This causes major trouble in unit tests, that access the file system.
>> All tests work if the test is started from the subproject directly.
>> In M1 the current work directory was always ${basedir}. Might be
>> related to MNG-1471.
> [ http://jira.codehaus.org/browse/MNG-1570?page=all ]
>
> Brett Porter closed MNG-1570:
> -----------------------------
>
> Assign To: Brett Porter
> Resolution: Won't Fix
>
> Maven 1.x only did this when forking.
OK. We always forked tests to avoid side-effects from the classpath, so I never
recognized a difference (I assume here that only the test was forked and not
the subproject by the reactor).
> Maven 2.x is not currently
> forking, so relative paths are correctly relative to user.dir.
Any plans for it? This seems quite essential. For our company this is a
show-stopper and as David Jackman explained in his posting it is also essential
if you have JNI bindings. I won't be able to convert the project for the swt
component of pico/nano too.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
