You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dmitry Katsubo (JIRA)" <ji...@codehaus.org> on 2010/09/09 12:55:33 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=234765#action_234765 ]
Dmitry Katsubo commented on MNG-2879:
-------------------------------------
@Paul Benedict: If this warning is an issue to be solved, why not to close it when Maven 3 is released?
I confirm the problem for IBM JDK (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32) and Maven 2.2.1 (r801777).
> 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 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.6
> Reporter: Brian Fox
> Assignee: Jason van Zyl
>
> 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