There's no need to create your own archetype -- I'm not sure where you got the idea that I'm telling you that you must do this. You are welcome to use the ones that exist, that's what most people do.
I was simply saying (suggesting) that you could/should fully specify the archetype (groupId, artifactId, and version) when creating a new project using an existing archetype. Wayne On 8/3/07, Craig Ching <[EMAIL PROTECTED]> wrote: > Thanks Wayne, I appreciate the help. Here I thought I was making good head > way on understanding maven and you throw this curve ball at me ;-) > > So, if I get what you're saying, I should first create my own archetype, > then I can create my projects based on that archetype by doing: > > mvn archetype:create \ > -DarchetypeGroupId=<archetype-groupId> \ > -DarchetypeArtifactId=<archetype-artifactId> \ > -DarchetypeVersion=<archetype-version> \ > -DgroupId=<my.groupid> \ > -DartifactId=<my-artifactId> > > > What are the benefits of creating and maintaining my own archetype? I > haven't really seen a need for this to this point, things had been going so > well ;-) > > Thanks again! > > Cheers, > Craig > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
