Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-2879

Thousands of [WARNING] Component returned which is not the same manager.

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.6
    • Fix Version/s: None
    • Component/s: Plugins and Lifecycle
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      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

        Issue Links

          Activity

          Hide
          Paul Benedict added a comment -

          If Plexus is truly being dumped for Maven 3, this issue will resolve as Won't Fix.

          Show
          Paul Benedict added a comment - If Plexus is truly being dumped for Maven 3, this issue will resolve as Won't Fix.
          Hide
          Jason van Zyl added a comment -

          Plexus will eventually be dropped for Guice, so no active development will be done in Plexus unless it's a blocker.

          Show
          Jason van Zyl added a comment - Plexus will eventually be dropped for Guice, so no active development will be done in Plexus unless it's a blocker.
          Hide
          Dmitry Katsubo added a comment -

          @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).

          Show
          Dmitry Katsubo added a comment - @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).
          Hide
          jieryn added a comment -

          Is Maven-2.2.1 no longer supported when Maven-3 comes along?

          Show
          jieryn added a comment - Is Maven-2.2.1 no longer supported when Maven-3 comes along?
          Hide
          Brett Porter added a comment -

          Maven 2.2.1 will be supported for some time (and for now we still support Maven 2.0.11), but there are unlikely to be new releases unless someone steps up to drive them or there are relevant patches to apply. Non-blocker fixes are unlikely to be backported.

          Show
          Brett Porter added a comment - Maven 2.2.1 will be supported for some time (and for now we still support Maven 2.0.11), but there are unlikely to be new releases unless someone steps up to drive them or there are relevant patches to apply. Non-blocker fixes are unlikely to be backported.

            People

            • Assignee:
              Jason van Zyl
              Reporter:
              Brian Fox
            • Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: