Hmm, yes there is a good chance I could fix it on the branch, I will
get that sorted.
Andy
On 13 Mar 2007, at 15:07, Jason van Zyl wrote:
On 13 Mar 07, at 6:53 AM 13 Mar 07, Andrew Williams wrote:
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.
I create a 1.0-alpha-9-stable branch so maybe we could slip it in
there. I just wanted to use the exact same container with a
detailed errata of what we fixed. The properties converter is the
only thing that's different right now, any change we could wedge
this fix in there too?
Jason.
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.JdkPrefixProfileAct
iva
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
