or you can drop it to the mojo-archetypes folder. Milos
On Wed, Jan 13, 2010 at 5:38 PM, Dan Tran <[email protected]> wrote: > Hi Julien, > > Welcome on board, > > If you introduce an archetype, then muti modules setup is needed. > > ie > > latext > pom.xml > latext-maven-shared > latext-maven-plugin > lalext-maven-achetype > > The shared project is optional, but I truely believe it is the way to > go so that other plugin/app can reuse your component directly > This is from my experience working with truezip and wagon ( have not > had time to split them yet ) > > -Dan > > On Wed, Jan 13, 2010 at 8:22 AM, Julien Ponge <[email protected]> > wrote: > > I would like to create an archetype for the latex-maven-plugin and I > > wonder what the mojo team best practices are... > > > > Is that ok to: > > 1. create an archetype subproject of the plugin, and > > 2. give it org.codehaus.mojo groupId / latex-archetype artifactId? > > > > Thanks > > > > -- > > http://izpack.org/ > > http://jpz-log.info/ > > http://julien.ponge.info/ > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
