Ah, sorry... Accidental send... The link I meant to include is: http://kickstyle.net/pebble/2006/07/19/1153358100000.html
I hope this helps. Also, if you create an archetype that might be useful to others and has to do with javaee, consider submitting it to https://maven-archetypes.dev.java.net/ On 11/19/06, Gregory Kick <[EMAIL PROTECTED]> wrote:
Anthony, I definitely understand the feeling of being lost while trying to create archetypes. I wrote up a small thing about dealing with packages that might be of some use. On 11/19/06, franz see <[EMAIL PROTECTED]> wrote: > > Good day to you, Anthony Ryan, > > A Maven Project needs to have a POM. Also, the diretory structure must > follow the standard set by maven (either that, or you tell maven that you're > using a different directory structure). > > When you create archetype, you would have to create its POM and follow the > directory structure just like any other maven project. Secondly, you would > have to create your prototype POM and prototype files. These prototypes are > what gets created when you do archetype:create. Also, you would have to > create an archetype descriptor (which describes the archetype to be > created). Lastly, you install (or deploy) it so that you can use it in your > archetype:create. > > In summary, you have a POM and files for the maven project of your > archetype. And some of these files are your achetype files (prototype POM, > prototype files, archetype descriptor). > > Cheers, > Franz > > > Anthony Ryan wrote: > > > > Hi, > > > > I'm new to using maven and want to set up a custom project template > > archetype that will create a specific file structure and put a few key > > documents in specific places at the start of each new project. > > > > The trouble I'm having is in setting up this archetype. I have read the > > guide at > > http://maven.apache.org/guides/mini/guide-creating-archetypes.html but it > > does not say if I already need to have this file structure created to > > install this archetype or if having the file paths written in the > > <sources> tags in the archetype file is enough. It also gives little > > information on why there are two pom.xml files in the example and what is > > the difference between them > > > > What are the steps in creating a custom archetype? Is it: > > 1.. Create archtype.xml with accompanying <sources> tags etc > > 2.. 'install' this archetype using mvn install > > 3.. Use archetype create to use this new archetype > > I apologise if this seems like a basic problem but there are few clear web > > pages written on the subject, > > > > Many thanks for any help, > > > > Anthony Ryan > > > > -- > View this message in context: > http://www.nabble.com/Creating-a-custom-archetype-tf2654228s177.html#a7430064 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Gregory Kick http://kickstyle.net/
-- Gregory Kick http://kickstyle.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
