[MNG-4356] [regression] Active component maps with stateful per-lookup components broken

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 11/Sep/09 14:16
• Updated: 11/Sep/09 18:38
• Resolved: 11/Sep/09 18:38

Description

The DefaultResourceManager from plexus-resources:1.0-alpha-5 holds a map of injected resource loaders. The resource loaders are stateful (for configuration purposes) and as such use per-lookup as their instantiation strategy. The configuration of the resource loaders is however lost because the container always looks up a new/different component when accessing the active component map (see PLX-434). This makes for instance the maven-remote-resources-plugin fail with Maven 3.