[ http://jira.codehaus.org/browse/ARCHETYPE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203726#action_203726 ]
Stevo Slavic commented on ARCHETYPE-273: ---------------------------------------- archetypeRepository (repository) and archetypeCatalog (catalog) are somewhat overlapping. Yes, docs are scarce, even in the [Maven book|http://www.sonatype.com/books/maven-book]. Luckily it's FOSS. I agree that either both parameters should be supported or just one, consistently. As proof of concept in my import-catalog mojo patch I implemented support just for one (repository). If there's no special reason to support both I'd prefer if it was just one that is left, maybe even just archetypeCatalog/catalog, it would make things more clear. Of course decision is up to plugin maintainers. IMO, in any case, repositoryId should be supported - repository URL (in form of repository or catalog) and repositoryId should go as a pair, just like in deploy:deploy-file mojo. > add goal to import remote archetype catalog into local catalog > -------------------------------------------------------------- > > Key: ARCHETYPE-273 > URL: http://jira.codehaus.org/browse/ARCHETYPE-273 > Project: Maven Archetype > Issue Type: New Feature > Components: Archetypes > Affects Versions: 2.0-alpha-4 > Reporter: Dan Allen > Attachments: > org.apache.maven.archetype.maven-archetype-ARCHETYPE-273_&_220_combo.patch > > > If I've just published a new archetype, I need to be able to provide the > developer with a command that allows them to "educate" their local catalog > about the new archetypes that area available. Currently, it's possible to > specify an archetype catalog for a single run of the generate goal: > mvn archetype:generate -DarchetypeCatalog=http://example.com/maven2 > But the catalog is transient. Those entries are not "remembered". The next > time I run the generate goal... > mvn archetype:generate > ...the archetypes in the catalog provided in the previous command are not > offered as options. > This is especially problematic when using an IDE to create a new Maven > project, because the mechanism for providing an archetype catalog differs in > each IDE. We want them to be in the local repository. Simply point, it's too > much information for the developer to have to reconcile, especially since > using an archetype is likely the developer's first exposure to your project. > It needs to be simple. > What I'm looking for is a command that I can give the developer to import the > entries from a remote archetype catalog. A discovery mechanism so to speak. > I envision the following sequence to work: > mvn archetype:import -DarchetypeCatalog=http://example.com/maven2 > mvn archetype:generate > At this point, the developer would see options for the imported archetypes. > The import goal could even download the archetype JAR files at the same time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira