[jira] Commented: (ARCHETYPE-242) The "remote" archchetype-catalog doesn't really exist.

["Stevo Slavic (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/ARCHETYPE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204123#action_204123 ] 

Stevo Slavic commented on ARCHETYPE-242:
----------------------------------------

Nexus Archetype Plugin will maintain archetype-catalog.xml for a given repository, once archetype artifact is deployed to that repository. If Nexus managed repository is a proxy/mirror of central, it will cache artifacts from central, but only ones that were used through mirror of central. Using latest archetype trunk (2.0-alpha-5-SNAPSHOT), archetype artifact can not be used without being first in an archetype catalog. So, remote (central) and all archetypes in central repository (except ones listed in archetype plugin internal archetype catalog) are useless unless archetype-catalog.xml is generated and maintained in central repository.

> The "remote" archchetype-catalog doesn't really exist.
> ------------------------------------------------------
>
>                 Key: ARCHETYPE-242
>                 URL: http://jira.codehaus.org/browse/ARCHETYPE-242
>             Project: Maven Archetype
>          Issue Type: Bug
>            Reporter: Jörg Henne
>            Priority: Minor
>
> This page http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-catalog.html states that the default "remote" catalog is located at http://repo1.maven.org/maven2/archetype-catalog.xml. However, there is no such file on repo1.maven.org and thus the remote catalog is useless.

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