You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcel Ammerlaan (JIRA)" <ji...@codehaus.org> on 2009/12/09 20:38:55 UTC
[jira] Commented: (MNG-2879) Thousands of [WARNING] Component
returned which is not the same manager.
[ http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201958#action_201958 ]
Marcel Ammerlaan commented on MNG-2879:
---------------------------------------
Also seeing this sometimes on IBM JDK 1.6.0 (sr5).
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@77537753
This is mostly happening during an EAR build.
> Thousands of [WARNING] Component returned which is not the same manager.
> ------------------------------------------------------------------------
>
> Key: MNG-2879
> URL: http://jira.codehaus.org/browse/MNG-2879
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.6
> Reporter: Brian Fox
> Assignee: Jason van Zyl
> Fix For: 2.2.x
>
>
> It happens when processing resources, mostly for war projects although I'm not 100% positive it's only wars. We see one of these warnings apparently for every file processed because sometimes there are just a few and sometimes there are 1000s correlating to the number of files in the project. So far it only happens on dual-core machines although not every time. It smells of a multithreading issue.
> This issue has already been fixed in PLX-287. This MNG issue is to try and get that fix into 2.0.x
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira