Vincent Massol wrote:
>Cool, I must have missed this new feature. How does it work?
>
>
Searches ".." (or a directory you can specify in the element).
If the file exists and versions match, it is used instead. Its the first
step towards a "workspace" style setup where projects know where the
ot
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 19 août 2005 15:40
> To: Maven Developers List
> Subject: Re: Processing Order for the m2 Reactor
[snip]
> >- You can't cd to a module and build it. You need to always buil
Vincent Massol wrote:
>I have also been a bit troubled by this too. The issues that I see with a
>parent-build-first strategy are:
>
>- It's the opposite of m1
>
>
ok
>- You can't cd to a module and build it. You need to always build the parent
>first so when you do development you often forget
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 19 août 2005 12:39
> To: Maven Developers List
> Subject: Re: Processing Order for the m2 Reactor
>
> so you are saying that the children should build before the parent?
>
so you are saying that the children should build before the parent?
Currently, the parent is considered a dep so it always goes first.
I see your point, which would mean making the modules dependencies
instead of the parent (though anything aggregating really should use
plugins able to deal with t
