[MNG-6327] Add ability to easily retrieve core extensions from alternative pluginRepository

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.5.2
• Component/s: Bootstrap & Build
• Assignee: Unassigned
• Reporter: Matt Biggs
• Created: 21/Dec/17 08:05
• Updated: 03/Jul/23 20:24
• Resolved: 03/Jul/23 20:24

Description

If you define an extension in .mvn/extensions.xml it is automatically retrieved and installed when you first build but ONLY if it is present in maven central.

I understand it's obviously a little 'chicken and egg' scenario but it would be really useful for making a seamless out of the box experience if it could either a) read the pom and use the pluginRepositories from there, or b) if you could perhaps specify the repository inside the extensions.xml file?

The only work around I can currently find is to ask the user to add an active profile to their settings.xml which obviously isn't as nice.

Issue Links

• is fixed by: MNG-5659 Project specific settings.xml
• is fixed by: MNG-6392 Add Project Settings .mvn/settings.xml
• is related to: MNG-5984 Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml
• is related to: MNG-6326 Build continues when core extensions aren't found
• relates to: MNG-6392 Add Project Settings .mvn/settings.xml