[MNG-836] plugin dependencies cannot be resolved

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-1
• Fix Version/s: 2.0-beta-1
• Component/s: Plugins and Lifecycle
• Assignee: Brett Porter
• Reporter: Kenney Westerhof
• Created: 05/Sep/05 06:30
• Updated: 10/Jun/09 15:07
• Resolved: 05/Sep/05 19:36

Description

Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.

Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
can be searched for the plugin's dependencies.

Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.

Issue Links

• relates to: MNG-2539 Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
• relates to: MNG-4191 separate plugin and artifact repositories