[MNG-3217] a plugin's dependencies can influence other plugins in a build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 2.1.0, 3.0-alpha-1
• Component/s: Artifacts and Repositories
• Assignee: Benjamin Bentmann
• Reporter: Brian E Fox
• Created: 20/Sep/07 17:57
• Updated: 10/Mar/16 13:54
• Resolved: 12/Feb/09 13:17

Description

See the linked issue for more details.

In short, the dependency plugin has declared a dependency on the site plugin (forget for now that this is probably not a good ide). The problem is that in doing this, the site plugin used for other things in the user's build is now pinned to the version declared in the dependency plugin. This seems to indicate some kind of pollution between what a plugin needs and what gets used for a build.

Issue Links

• is related to: MDEP-113 Unable to find the mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-SNAPSHOT
• relates to: MNG-3284 Cached plugins are used, even when the specifically declared