[MNG-4191] separate plugin and artifact repositories

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Assignee: Benjamin Bentmann
• Reporter: Igor Fedorenko
• Created: 08/Jun/09 14:45
• Updated: 07/Apr/10 03:01
• Resolved: 20/Jun/09 10:34

Description

MavenProject has single remoteArtifactRepositories member that is used to resolve both application dependencies and plugin dependencies. Need to separate the two.

Issue Links

• is duplicated by: MNG-3540 No plugin update from a staged repository
• is related to: MNG-229 plugin repository separation mixup
• is related to: MNG-836 plugin dependencies cannot be resolved
• is related to: MNG-2539 Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
• relates to: MNG-4302 Physically separate plugins (and their dependencies) from project artifacts/dependencies in the local repository
• supercedes: MNG-2750 Remove the notion of pluginRepositories