[
https://issues.apache.org/jira/browse/MNG-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318058#comment-16318058
]
Matt Biggs commented on MNG-6327:
---------------------------------
The great thing about the extensions.xml file is it can be checked in to git
giving all users the same setup. Unfortunately you can't do that with the
settings.xml file so that then relies on me trying to get all users to
configure their settings.xml file correctly.
The profile part was a little misleading, it was just what I used to add our
company nexus repository. I added the profile and then added a <activeProfiles>
section. When you say add the repository manager did you mean via a mirror? I
just wasn't aware of any other mechanism other than the profile or the mirror
within settings.xml.
> Add ability to easily retrieve core extensions from alternative
> pluginRepository
> --------------------------------------------------------------------------------
>
> Key: MNG-6327
> URL: https://issues.apache.org/jira/browse/MNG-6327
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 3.5.2
> Reporter: Matt Biggs
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
