[MNG-1949] project-level plugin dependencies not handled correctly in multimodule builds

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.1
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: John Dennis Casey
• Created: 09/Jan/06 18:45
• Updated: 28/Mar/10 17:39
• Resolved: 28/Mar/10 17:39

Description

plugin containers are only initialized once per build, which means they may contain incorrect project-introduced dependencies for project Y in a multimodule build (polluted by project X predecessor). We should look at ways of dumping plugin containers with project-specific configurations, or else providing a container overlay to handle project-specific dependencies, etc.

NOTE: This is tied into the notions of build extensions, which will have similar consequences on the core container.

Issue Links

• duplicates: MNG-1323 Plugin extensions (dependencies) not resolved in reactor build
• is duplicated by: MNG-1836 inherited plugin dependencies
• is related to: MNG-1024 Reactor does not allow multiple plugin versions across projects
• relates to: MNG-1323 Plugin extensions (dependencies) not resolved in reactor build