[
http://jira.codehaus.org/browse/ARCHETYPE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204898#action_204898
]
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
(http://markmail.org/message/remgjzpl2kdrd7ph?q=+Error+reading+archetype+catalog+http://repo1.maven.org/maven2&page=1&refer=2cb3yjsdlzym52vb)
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: 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
