Hi all!
On 10/13/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
There are some instances where you want to put logs in the correct
folder but if you use . Then a multimodule build will end up putting
them in the wrong place. The best you can do is pass a property to
something and pass ${basedir}. As far as changing the working folder in
the vm, I don't think it's possible.
After your replies and some consideration I choose the "${basedir} as
system property"-approach, and it does the trick. For non-maven
executions I use the "user.dir" as a backup. I really dislike
programming with system properties, but in this case I guess I have no
choice.
Thank you!
/Daniel
-----Original Message-----
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 6:14 PM
To: Maven Developers List
Subject: Re: [m2] Multiproject execution directory
Yes, project should not depend on where it is executed.
What is your usecase? (ie why you really need it? )
-D
On 10/12/06, Daniel Brolund <[EMAIL PROTECTED]> wrote:
>
> Hello!
> When running multi-project/multi-module/sub-module builds, does maven2
> use the execution directory of the aggregating project for /all/
> projects?
>
> If so, is it possible to make sure each sub-projects is being run in
> its own root?
>
> I use a flat (eclipse-like) project structure:
>
> project1/
> project2/
> aggregating_project/
>
> and
>
> <modules>
> <module>../project1</module>
> <module>../project2</module>
> </modules>
>
> in the aggregating_project pom.xml.
>
> I know, "you shouldn't depend on the execution directory" etc, but
> this time I really need it.
>
> I've tried googling for this, but with no success so far.
> I've also tried the users list, but I got drowned...
>
> Cheers
> Daniel
>
> --
> __________________________
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> 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]
--
__________________________
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
