Stuart McCulloch wrote:
> On 10 Jan 2013, at 13:19, Kristian Rosenvold wrote:
[snip]
>> In one way kind of neat; since the statement has "both"
>> @plexus.requirement and final it's fairly obvious who sets it;
>> although the semantics are definitely not java101 ;) Do you know if
>> this works w
On 10 Jan 2013, at 13:19, Kristian Rosenvold wrote:
> 2013/1/10 Stuart McCulloch :
>> There's no guarantee that Plexus field injection will be synchronized, so if
>> you're constructing an object in one thread and immediately handing it off
>> to another >thread without any intervening synchroni
2013/1/10 Stuart McCulloch :
> There's no guarantee that Plexus field injection will be synchronized, so if
> you're constructing an object in one thread and immediately handing it off to
> another >thread without any intervening synchronization then you should use
> volatile fields or ideally i
On 10 Jan 2013, at 07:57, Kristian Rosenvold wrote:
> It seems like I made some kind of mistake in my initial analysis, so
> it looks better !
>
> Used from core, the wagons are consistently created on one thread and
> handed off to another. From the handoff they seem to be confined to
> that thr
2013/1/9 Dennis Lundberg :
> What do you mean with "not used"?
doesn't work so not used :-)
I will revert that and try to fix changes plugin configuration.
>
> On 2013-01-07 21:51, ol...@apache.org wrote:
>> Author: olamy
>> Date: Mon Jan 7 20:51:49 2013
>> New Revision: 1429997
>>
>> URL: http:/
