maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <j...@codehaus.org>
Subject [jira] (ARCHETYPE-431) Only include Apache Maven archetypes in internal archetype catalog
Date Sun, 07 Jul 2013 22:30:05 GMT

    [ https://jira.codehaus.org/browse/ARCHETYPE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328142#comment-328142
] 

Arnaud Heritier commented on ARCHETYPE-431:
-------------------------------------------

[~afloom] I'm interested to release the archetype 2.3 soon but this issue is always opened,
what can we do ?
About the internal catalog when do we use it (I didn't review the code for now)?
Aren't we using the one from central by default ? (http://search.maven.org/remotecontent?filepath=archetype-catalog.xml)
The internal is used only if the one from central cannot be downloaded ? (I that case we may
suppose that the user will have difficulties to download the plugin itself)
                
> 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

Mime
View raw message