Barrie,
Honestly, the purpose of my email about splitting the list was not to
return attention to this thread :-)
You are correct that my thought process when I wrote that did not take
into account the possibility of sparse checkouts.
What I learned from that thread and other discussions was the
On Sun, Dec 12, 2010 at 10:45 AM, Benson Margulies
wrote:
> On Sat, Dec 11, 2010 at 7:05 PM, Benjamin Bentmann
> wrote:
>> Benson Margulies wrote:
>>
>>> Say that, in a parent pom, there is an execution of a plugin that sets
>>> a property. (e.g. the build helper plugin's port reserver).
>>>
>>>
In my defense, I was busy coding a plugin when I posed the question.
On Sun, Dec 12, 2010 at 5:49 PM, Brett Porter wrote:
> You're probably better using the available plugin expressions for the
> execution root rather than this.
>
> Also, the users@ list is the right place to ask the original qu
You're probably better using the available plugin expressions for the execution
root rather than this.
Also, the users@ list is the right place to ask the original question :)
Cheers,
Brett
On 12/12/2010, at 11:15 AM, Benson Margulies wrote:
> On Sat, Dec 11, 2010 at 7:05 PM, Benjamin Bentmann
On Sat, Dec 11, 2010 at 7:05 PM, Benjamin Bentmann
wrote:
> Benson Margulies wrote:
>
>> Say that, in a parent pom, there is an execution of a plugin that sets
>> a property. (e.g. the build helper plugin's port reserver).
>>
>> Will those properties inherit down to the children?
>
> No, the runti
Benson Margulies wrote:
Say that, in a parent pom, there is an execution of a plugin that sets
a property. (e.g. the build helper plugin's port reserver).
Will those properties inherit down to the children?
No, the runtime data of project instances is separated.
Benjamin
--
Say that, in a parent pom, there is an execution of a plugin that sets
a property. (e.g. the build helper plugin's port reserver).
Will those properties inherit down to the children?
-
To unsubscribe, e-mail: dev-unsubscr...@mave
