Archetypes are initial templates of a project, they just provide an initial layout and pom, but no build time functionality, and cannot be reapplied.
Plugins provide buildtime actions >From your initial description, you want the latter... You might, after you have created your plugin, create an archetype to show how to create/use your plugin in a project. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On Feb 20, 2012 12:46 p.m., "ecniv" <vince.leguill...@gmail.com> wrote: > Hum, plugin is one possibility indeed. > > Why not using a custom archetype ? What are the advantages / drawbacks of > each solution (plugin VS archetypes / pom)? > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-for-XML-project-tp5498778p5498911.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
