[
https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046531#comment-16046531
]
Yuri commented on MNG-5820:
---------------------------
I am wondering why such change would break backwards compatibility. Wouldn't
this mean basically a new, optional <extensions> element along side <servers/>,
<profiles/> etc?
{code:xml}
<extensions>
<extension>
<groupId>io.takari.polyglot</groupId>
<artifactId>polyglot-ruby</artifactId>
<version>0.1.5</version>
</extension>
</extensions>
{code}
> Allow extensions in settings.xml
> --------------------------------
>
> Key: MNG-5820
> URL: https://issues.apache.org/jira/browse/MNG-5820
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 3.3.1
> Reporter: Yuri
> Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> Since 3.3.1, we are now allowed to specify extensions in the
> projectBaseDir/.mvn/extensions.xml. This is great on it's own, but I have a
> case where repo urls are externalized to ~/.m2/settings.xml and these urls
> require an extension. Right now, the url and the extension that goes along
> with it are managed in two completely different places.
> Ideally, I would like to see the option to add an extension to our existing
> ~/.m2/settings.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
