maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalle Korhonen (JIRA)" <>
Subject [jira] Commented: (ARCHETYPE-242) The "remote" archchetype-catalog doesn't really exist.
Date Sat, 02 Jan 2010 22:03:55 GMT


Kalle Korhonen commented on ARCHETYPE-242:

Agree with Stevo, it's still pretty badly broken. MRM doesn't help much if you want to make
your archetype available publicly to other users like many open source projects do. There
was a discussion about this on Maven users list (
almost a year ago noting that repo1/repo2 should either just run archetype:crawl periodically
or Sonatype's Nexus should push the catalog to repo1 but I don't know if either effort has
gone anywhere. Considering archetype:create is already deprecated I think this is more than
a minor issue. Right now, is there any better workaround than lobby archetype maintainers
to include your archetype in the new version of archetype plugin?

> The "remote" archchetype-catalog doesn't really exist.
> ------------------------------------------------------
>                 Key: ARCHETYPE-242
>                 URL:
>             Project: Maven Archetype
>          Issue Type: Bug
>            Reporter: Jörg Henne
>            Priority: Minor
> This page
states that the default "remote" catalog is located at
However, there is no such file on 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:
For more information on JIRA, see:


View raw message