Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <6673225.21541240322085003.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Tue, 21 Apr 2009 08:54:45 -0500 (CDT)
From: "Arne Kepp (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Commented: (MNG-2879) Thousands of [WARNING] Component
 returned which is not the same manager.
In-Reply-To: 
 <54290723.1174072294455.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173665#action_173665 ] 

Arne Kepp commented on MNG-2879:
--------------------------------

I believe I am seeing the same thing while compiling trunk of GeoServer ( running mvn clean install -Pweb2 )

java -version
java version "1.5.0_18"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_18-b02)
Java HotSpot(TM) Server VM (build 1.5.0_18-b02, mixed mode)

mvn -version
Maven version: 2.0.10
Java version: 1.5.0_18
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

(Ubuntu 9.04 i386)

> 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.1.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