maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <>
Subject [jira] (ARCHETYPE-431) Only include Apache Maven archetypes in internal archetype catalog
Date Wed, 10 Jul 2013 08:48:05 GMT


Anders Hammar commented on ARCHETYPE-431:

@Arnaud: The internal catalog is used if explicitly chosen or if we fail to connect to the
central catalog. What is left to do in this ticket is some cleanup. We need to correct the
text in the wiki page linked to above and also look into the junit test case class that does
"something" (don't remember what, it might verify it) with the internal catalog file.
I'm not sure when, or even if, I would have time to do this in the near future.
> Only include Apache Maven archetypes in internal archetype catalog
> ------------------------------------------------------------------
>                 Key: ARCHETYPE-431
>                 URL:
>             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:

View raw message