[MNG-1928] ignores pluginRepository in settings.xml, honors in POM

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.1
• Component/s: Plugins and Lifecycle
• Environment: mvn 2.0.1, jvm 1.5.0_05, OSX 10.4.3
• Assignee: Brett Porter
• Reporter: Ryan Marsh
• Created: 05/Jan/06 21:27
• Updated: 07/Sep/07 00:15
• Resolved: 07/Sep/07 00:15

Description

if specified in the POM as a plugin repo, maven can use the team.andromda.org/maven2 repo for finding, downloading, and installing plugins.
however, settings.xml ignores plugin repos and only checks central if the plugin has never been downloaded before.

for instance. if settings.xml has a pluginRepository entry for team.andromda.org/maven2 then:
mvn andromdapp:generate
should download the andromdapp plugin from our repo. but it doesn't. only central is checked and it fails to find the plugin.

Issue Links

• duplicates: MNG-3099 Profiles ignored when working with non-projects (such as archetype:create)
• relates to: MNG-874 Cannot download plugin POM when auto-discovering plugins