[
https://issues.apache.org/jira/browse/ARCHETYPE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed ARCHETYPE-463.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> order versions when selecting archetype in batch mode
> -----------------------------------------------------
>
> Key: ARCHETYPE-463
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-463
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 2.2
> Reporter: Stuart McCulloch
> Priority: Major
>
> ARCHETYPE-325 added sorting of archetypes by version when running in
> interactive mode. However when running in batch mode, if the archetype
> version is not defined the plugin just takes the first entry in the catalog
> that matches the requested archetypeGroupId and archetypeArtifactId. This
> might not be the latest archetype version depending on the catalog ordering.
> Ideally the DefaultArchetypeSelector would use a similar approach to that
> used in ARCHETYPE-325 to find the latest version for a given groupId and
> artifactId in the catalog and then use that as the archetypeVersion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
