maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5820) Allow extensions in settings.xml
Date Mon, 12 Jun 2017 16:48:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046765#comment-16046765
] 

Karl Heinz Marbaise commented on MNG-5820:
------------------------------------------

Having an extensions entry in your {{settings.xml}} can only being read by a version which
supports this. All earlier versions would fail with that This means breaking backwards compatibility.


> 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)

Mime
View raw message