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.JdkPrefixProfileActivat > [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]
