[
http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184932#action_184932
]
Justin K edited comment on MNG-2879 at 7/26/09 6:53 PM:
--------------------------------------------------------
I get the same issue on Suse Linux running the IBM JDK (J9 with Maven 2.2.0.
The build works correctly, but hundreds of these messages are given. For
example:
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@1e161e16
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@16161616
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@153e153e
was (Author: justink):
I get the same issue on Suse Linux running the IBM JDK (J9). The build
works correctly, but hundreds of these messages are given. For example:
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@1e161e16
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@16161616
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@153e153e
> 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
