[
https://jira.codehaus.org/browse/ARCHETYPE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Hammar reopened ARCHETYPE-431:
-------------------------------------
Just found this:
http://docs.codehaus.org/display/MAVENUSER/Archetypes+List
I don't think we should try to keep track of all existing archetypes. Maybe we
could keep this page for archetypes creators to modify, but not compare the
internal catalog to this one.
Seems there is more to do here. Also, there is a junit test case to
modify/remove.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
