Hi, 2007/5/30, Kenney Westerhof <[EMAIL PROTECTED]>:
Hi, That kind of metadata is not handled by packaging, but by the artifact manager. What do you need this for? If it's to automatically list all available archetypes, that would be great.
You guessed \o/ Currently, the selection mojo is based on the same mecanism as the maven plugins. In interractive mode, it: - ask for a group from a list (org.apache.maven.archetypes and org.codehaus.mojo.archetypes) - retrieves the group metadata - ask for an archetype found in the metadata (construct a list) - retrieves the artifact metadata - ask for the version found in the metadata (construct a list) I would like to have a new maven-archetype packaging (currently working on) Concerning the issue of packaging, metadata and archetype selection from lists, i have some options: - mimics the plugin metadatas (in groups) but changing the name of the metadata file in repo - using the plugin metadatas, this implies to have plugins and archetypes in separate groups - have a per repository registry (xml or other) that holds the archetypes metadatas for the whole repository this implies to have a way to 'merge' information from many repos in the local repo (to be used offline) WDYT? Raphaël We should generalize that by having a special kind of metadata in special
groups, like org/apache/maven/metadata/(metadata-group)/ or similar, so we can centrally store package handlers, plugin metadata, archetypes etc. spanning different groupId's. There'd be a central place (groupid) in each repository for storing that information. If you need this for something totally different, then n/m the above, just wanted to pitch this in since it's been on my mind for a while now. -- Kenney Raphaël Piéroni wrote: > Hi > > if i would create a new packaging for archetypes, > what is the way (i don't need doco link about lifecycle hook > of a mojo, i already know it ;) ) > to have a specific metadata uploaded as long with the > artifact during the install and deploy phases. > > My point is how to create metadata and how to > have them automagically uploaded; > > for a group, say org.apache.maven.archetypes, > and an archetype, quickstart-archetype, at version 1.0 > i need a metadata in the org/apache/maven/archetypes > directory, and in org/apache/maven/archetypes/quickstart-archetype > just like the maven-plugins. > > Many thanks for any help. > > Regards > > Raphaël --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
