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

Posted to issues@archiva.apache.org by "Stefan Wendelmann (JIRA)" <ji...@apache.org> on 2019/04/26 12:00:00 UTC

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

    [ https://issues.apache.org/jira/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826914#comment-16826914 ] 

Stefan Wendelmann commented on MRM-1284:
----------------------------------------

It has been 9 1/2 years now? 
Are there any efforts to fix that issue ?
Or do we need to migrate to other OS Maven Repository Manager like nexus or jfrog?

> Support for archetype-catalog.xml
> ---------------------------------
>
>                 Key: MRM-1284
>                 URL: https://issues.apache.org/jira/browse/MRM-1284
>             Project: Archiva
>          Issue Type: New Feature
>          Components: indexing
>            Reporter: Mike Haller
>            Priority: Major
>             Fix For: 3.1.0
>
>
> 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
(v7.6.3#76005)