maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-4645) Move central repo definition out of Maven's core so it can be more easily changed
Date Mon, 11 Dec 2017 16:35:20 GMT

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

Hudson commented on MNG-4645:
-----------------------------

Build unstable in Jenkins: Maven TLP (wip) » maven » pre-reset-master #3

See https://builds.apache.org/job/maven-wip/job/maven/job/pre-reset-master/3/

> Move central repo definition out of Maven's core so it can be more easily changed
> ---------------------------------------------------------------------------------
>
>                 Key: MNG-4645
>                 URL: https://issues.apache.org/jira/browse/MNG-4645
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 3.3.3
>            Reporter: Paul Gier
>
> The Maven central repository is currently a hidden default repository available to Maven.
 The configuration of the central repo can be changed only if you know the (somewhat obscure)
repository id "central".  It would be better if the configuration of the central repository
was moved from the Maven internals to the default settings.xml.  This way the repository would
still be available to a default Maven install, but would also be clear to users how the central
repo is configured in case it needs to be changed for mirror settings or some other reason.
 It would also make the repository ordering in the settings more clear.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message