[M2] Multiproject and ${user.dir} (was: [jira] Closed: (MNG-1570) Testing from a parent POM fails ...)

[Jörg Schaible <Jo...@Elsag-Solutions.com>]

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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] Multiproject and ${user.dir} (was: [jira] Closed: (MNG-1570) Testing from a parent POM fails ...)

[Brill Pappin <jo...@gmail.com>]

I'm having this problem as well... modules all build fine on their
own, but I can't reference a module relative path properly when
starting a reactor build from the parent.

- Brill Pappin

On 11/24/05, Brett Porter <br...@gmail.com> wrote:
> On 11/23/05, Jörg Schaible <Jo...@elsag-solutions.com> wrote:
> > > 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.
>
> Someone took a stab at implementing it and then seems to have
> disappeared from the list, so we're hoping to pick it up soon.
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: [M2] Multiproject and ${user.dir} (was: [jira] Closed: (MNG-1570) Testing from a parent POM fails ...)

[Brett Porter <br...@gmail.com>]

On 11/23/05, Jörg Schaible <Jo...@elsag-solutions.com> wrote:
> > 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.

Someone took a stab at implementing it and then seems to have
disappeared from the list, so we're hoping to pick it up soon.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org