[
https://issues.apache.org/jira/browse/MNG-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314916#comment-16314916
]
Karl Heinz Marbaise commented on MNG-6327:
------------------------------------------
Maybe I misunderstand a thing here but if you configure your setup to use a
repository manager in your {{settings.xml}} there is no need for a profile ?
Apart from that extensions will be resolve from the repositories like plugins /
dependencies...?
The problem you mentions to read the pom is really a *chicken and egg* cause
at the time of reading the {{.mvn/extensions.xml}} the pom's have not been read
cause by using extensions you can influence that.. and going to the path
reading the pom and using things like pluginRepositories from there that would
break things like takari etc.
> 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)
