Hrm, that's a bummer. Thanks for looking into it. Is there any
possibility of patching a version that can run on 2.0.x? I'd be willing
to take something and use it internally if needed, if a patch is
possible. 

-----Original Message-----
From: Andrew Williams [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 13, 2007 9:54 AM
To: Maven Developers List
Subject: Re: "Component returned which is not the same manager" ?

It is possible that the error was slowing things down, as returning the
wrong manager could cause a tree to be traversed rather than returning
the first leaf.

Getting it into 2.0.6 is not very likely, as it is cutting edge
container which I don't think is slated to move to the 2.0.x branch.  
I will investigate further and see what can be done.

Andy

On 13 Mar 2007, at 12:58, Brian E. Fox wrote:

> Thanks Andy! When you found the problem, does it make sense that it 
> was causing my builds to slow down even when I disabled the warning 
> output?
>
> Is there any chance we can get this in 2.0.6?
>
> -----Original Message-----
> From: Andrew Williams [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 13, 2007 7:17 AM
> To: Maven Developers List
> Subject: Re: "Component returned which is not the same manager" ?
>
> I fixed this last week, and is now released in plexus-containers 1.0- 
> alpha-19.
> This fix is present in maven-2.1-SNAPSHOT also.
>
> Andy
>
> On 27 Feb 2007, at 14:47, Brian E. Fox wrote:
>
>> I've been seeing this forever, it's very annoying. It significantly 
>> slows down our build when this happens, something along the lines of 
>> 20
>> -> 40 minutes (100% increase). I thought it was because of all the
>> logging so I recompiled that jar to remove the warning but it is 
>> still slow when it happens. I think it could be that since the object

>> isn't returned to the correct manager, it isn't able to reuse them 
>> correctly and results in an explosion of object creation. The 
>> original issue
>> is:
>> http://jira.codehaus.org/browse/PLX-287
>>
>> -----Original Message-----
>> From: Andrew Williams [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, February 27, 2007 6:21 AM
>> To: Maven Developers List
>> Subject: Re: "Component returned which is not the same manager" ?
>>
>> This is a plexus bug, registered on JIRA already.
>> Not sure if anyone knows what is causing it, but there is one 
>> possible related change being looked into I believe.
>>
>> A
>>
>> On 27 Feb 2007, at 02:39, Jason Dillon wrote:
>>
>>> Anyone know what this means?
>>>
>>> <snip>
>>> [WARNING] Component returned which is not the same manager.
>>> Ignored.
>>> component=org.apache.maven.profiles.activation.JdkPrefixProfileActiv
>>> a
>
>>> t
>>
>>> [EMAIL PROTECTED]
>>> </snip>
>>>
>>> I'm seeing a tone of these in the Geronimo build... seems to happen 
>>> randomly from build to build.  I ran one build and did not see this,

>>> then I started up a new build and I see like 1000x of these?
>>>
>>> Anyone know?
>>>
>>> --jason
>>>
>>> --------------------------------------------------------------------
>>> -
>>> 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]
>>
>>
>> ---------------------------------------------------------------------
>> 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]
>
>
> ---------------------------------------------------------------------
> 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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to