You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2013/05/15 10:31:52 UTC

[jira] (ARCHETYPE-427) Archetype catalog should be retrieved from all defined remote repositories and not only central

     [ https://jira.codehaus.org/browse/ARCHETYPE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Hammar updated ARCHETYPE-427:
------------------------------------

    Fix Version/s:     (was: 2.3)
                   3.0
    
> Archetype catalog should be retrieved from all defined remote repositories and not only central
> -----------------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-427
>                 URL: https://jira.codehaus.org/browse/ARCHETYPE-427
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Generator
>    Affects Versions: 2.2
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Anders Hammar
>             Fix For: 3.0
>
>
> Instead of just retrieving the catalog from the central repo (hard-coded url), it should use all defined remote repositories (in settings.xml and possibly even an existing pom.xml). This is useful in a more advanced environment where there might be several repositories involved, which all could contain (different) archetype catalogs.
> On top of this, mirror, proxy, and authentication info from settings.xml should be honored.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira