IIUC, you're using archetype:generate in interactive mode, which does only
propose versions in archetype-catalog.xml
Having version in this catalog is a simple solution in the code (no complex
resolution or repository access), but yes, this can be limitating: perhaps we
could add an option in
Hello Maven users,
What's the purpose of archetype-catalog.xml file (especially on
central repo) except to fall out of sync with archetype artifacts in
the repository and prevent them from being used (easily)?
E.g. central now has several Cargo 1.1.0 archetypes but they can not
be resolved from
