You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2014/08/08 06:16:11 UTC
[jira] (MRM-1284) Support for archetype-catalog.xml
[ https://jira.codehaus.org/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRM-1284:
------------------------------
Fix Version/s: (was: 2.1.1)
2.1.2
> Support for archetype-catalog.xml
> ---------------------------------
>
> Key: MRM-1284
> URL: https://jira.codehaus.org/browse/MRM-1284
> Project: Archiva
> Issue Type: New Feature
> Components: indexing
> Reporter: Mike R. Haller
> Fix For: 2.1.2
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)