2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:
> > > what's the difference ? > Mainly > - the descriptor is changed > - user is prompted for selecting the archetype and configuration > (unless using -B) > - any file can be resolved as packaged (using package in the directory > resolution) > - any file can be resolved as binary (copied instead of velocity template) > - support for multi project
I forgot: - archetype creation form an existing project (yes with the above features packaged, filtered, multiproject)
> > > > > http://mojo.codehaus.org/maven-archetypeng/ > which is not yet released Did you have a roadmap when it will be released ?
I got a roadmap (on paper without any date) But i could say it need at least 2 weeks before putting a first alpha release Raphaël
So, if I understand, maven-archetypeng has more features and seems more powerful. So it's better to look at maven-archetypeng instead of maven-archetype. I will have a look. I imagine it will normally replace maven-archetype in the future. > > > or > > > > mvn archetype:create > > -DgroupId=[your project's group id] > > -DartifactId=[your project's artifact id] > > -DarchetypeArtifactId=maven-archetype-archetype > > > > > > (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html) > > > Hope the answer makes sense Nice thanks. Rémy
