You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (JIRA)" <ji...@codehaus.org> on 2009/06/26 00:08:54 UTC

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

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

Tamás Cservenák commented on ARCHETYPE-242:
-------------------------------------------

Not quite true. Central is meant only as "convenience" artifact source, nobody should use it directly anyway. All Maven users should use some sort of MRM (Maven Repository Manager, http://maven.apache.org/repository-management.html)

For example, using Nexus OSS or Pro (http://nexus.sonatype.org/) together with Nexus Archetype Plugin (https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin) gives you exactly that: "live" archetype catalogs. When you deploy an archetype, it immediately gets listed in catalog, and is available to all other consumers of the 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