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 version selection UI to "search versions in repository", or more simple "free version" where you enter the version you want Please open a Jira issue. And if you can, attach a patch and test cases :)
A workaround should be to use the batch mode: see [1] Less user-friendly than "free version", but already available. Regards, Hervé [1] http://maven.apache.org/archetype/maven-archetype- plugin/examples/generate-batch.html Le dimanche 8 mai 2011, Stevo Slavić a écrit : > 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 central as archetypes by maven archetype plugin 2.0 > because they are not listed in archetype-catalog.xml (latest there is > 1.0.6). To use these archetypes (in repo but not in catalog) one has > to resolve them first as plain dependencies, have maven crawl local > repo, and then use them as archetypes from local repo. > > Why couldn't archetype artifacts be treated as any other plain Maven > artifacts, why do they need to be cataloged? > > Regards, > Stevo. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
