[
http://jira.codehaus.org/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270634#comment-270634
]
Jarrod Roberson commented on MRM-1284:
--------------------------------------
this should really get fixed where it generates an archetype-catalog.xml file
available at the root of the server that is either generated on uploads and
deletes or dynamically to support custom archetypes seamlessly uploaded to the
repositories. Right now I have to manually edit a file at the
/opt/archiva/apps/archiva/archetype-catalog.xml location.
> 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
> Fix For: 1.4
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
