RIght, *you* didn't say that, that was the impression I got from the link. ;-)
But that got me to this page: http://maven.apache.org/plugins/maven-archetype-plugin/usage.html which showed me this: mvn archetype:create -DgroupId=sample.group.id \ -DartifactId=sample-artifact-id \ -Dversion=1.0-SNAPSHOT \ -DpackageName=sample.group.id \ -DarchetypeGroupId=org.apache.maven.archetypes \ -DarchetypeArtifactId=maven-archetype-quickstart \ -DarchetypeVersion=1.0-SNAPSHOT which appears to be what I was trying to do I guess. There are a few things I wasn't aware of by executing the shortcut method. I wasn't aware that I was in fact using the maven-archetype-quickstart archetype and I wasn't aware that the archetype version is something I'd need to maintain, that's something I view as one more detail that I'd rather not have to maintain. I guess the right way to do this is to create scripts that wrap these operations for my developers. Thanks for the help! Cheers, Craig On 8/3/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > 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] > >
