You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2015/02/04 21:28:18 UTC
[jira] (ARCHETYPE-431) Only include Apache Maven archetypes in
internal archetype catalog
[ https://jira.codehaus.org/browse/ARCHETYPE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362552#comment-362552 ]
Anders Hammar commented on ARCHETYPE-431:
-----------------------------------------
What I will do is remove the coupling of the wiki page listing archetypes to the internal catalog. The code that generates the internal catalog from the wiki will be removed.
A separate ticket will be created to handle the outdated wiki page listing "all" archetypes.
> Only include Apache Maven archetypes in internal archetype catalog
> ------------------------------------------------------------------
>
> Key: ARCHETYPE-431
> URL: https://jira.codehaus.org/browse/ARCHETYPE-431
> Project: Maven Archetype
> Issue Type: Task
> Components: Generator
> Affects Versions: 2.2
> Environment: n/a
> Reporter: Anders Hammar
> Assignee: Anders Hammar
> Priority: Minor
> Fix For: 2.3
>
>
> Currently the internal archetype catalog includes archetypes from different projects. However, there are new archetypes added to the Maven echo-system daily and deciding which to include (and keep it up-to-date) will be impossible. The best solution would the be to just include the "official" archetypes from the Maven team.
> We should also update the versions here and not use "RELEASE" as version as it is deprecated.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)