You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Mike R. Haller (JIRA)" <ji...@codehaus.org> on 2009/11/24 14:24:55 UTC

[jira] Commented: (MRM-1284) Support for archetype-catalog.xml

    [ http://jira.codehaus.org/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199203#action_199203 ] 

Mike R. Haller commented on MRM-1284:
-------------------------------------

See also MNGECLIPSE-1152

> Support for archetype-catalog.xml
> ---------------------------------
>
>                 Key: MRM-1284
>                 URL: http://jira.codehaus.org/browse/MRM-1284
>             Project: Archiva
>          Issue Type: New Feature
>          Components: indexing
>            Reporter: Mike R. Haller
>
> When creating new archetypes for custom type of projects, the archetypes need to be published (deployed) to a repository. However, to use the archetypes (e.g. in M2Eclipse), you need to set an URL for a remote archetype-catalog.xml
> Archiva should be able to (dynamically) produce the contents of an archetype-catalog.xml based on (all) of the archetypes deployed in the given repository. This would enable teams to use their own archetypes more efficiently.

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