maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaël Piéroni (JIRA) <j...@codehaus.org>
Subject [jira] Closed: (ARCHETYPE-179) repo1 is hardcoded into internal catalog
Date Thu, 05 Jun 2008 20:45:13 GMT

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

Raphaël Piéroni closed ARCHETYPE-179.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-alpha-4

Fixed since revision 663729
The internal catalog is fixed

The test case retrieving the catalog from wiki also. 
It also tries for each archetype defined to use it with first RELEASE then the defined version.


> repo1 is hardcoded into internal catalog
> ----------------------------------------
>
>                 Key: ARCHETYPE-179
>                 URL: http://jira.codehaus.org/browse/ARCHETYPE-179
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Generator
>            Reporter: Brett Porter
>             Fix For: 2.0-alpha-4
>
>
> The repository URL should not be hardcoded into the internal catalog - it is looking
at repo1, when really it should be looking at the repository defined by central (ie, the one
in my settings file that points to my internal repository proxy). So, it needs to honour settings.
I believe the catalog should specify an id and a url - and if the id exists use that instead
(and if not, fall back to the URL).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message