Hi guys, I would like to close some issues.
Some [1] because the release of the archetype plugin version 2.0-alpha has answered the needs. And some others [2] that are obsoleted by the archetype plugin version 2.0-alpha. Please feel free to comment on each issue by telling why i should not close it. Next week, i will close each of the issues on which we have a consensus (even a lazy one). This vote is open until Monday 25 March 2008. Regards, Raphaël [1] closed by 2.0-a: ARCHETYPE-31 Create a tool that will generate an archetype from an existing project ARCHETYPE-79 Project namespaces not added to sub projects ARCHETYPE-70 Add project description as a mojo parameter ARCHETYPE-108 Use of wildcards in archetype.xml ARCHETYPE-54 Dynamic archetype resource ARCHETYPE-37 Simplify archetype creation when there are many archetype resources ARCHETYPE-119 Ability to Create directories and files above /src ARCHETYPE-96 placeholder wrong in generated files ARCHETYPE-65 Restore the ability to "package" non-Java resources ARCHETYPE-71 Allow for more flexable directory strucuture in custom archetype ARCHETYPE-62 Allow package.html files to be included in an archetype ARCHETYPE-52 can't use .cvsignore as resource ARCHETYPE-58 Allows for additional properties in velocity context and also conditional processing of source, resources etc ARCHETYPE-63 Provide more properties (like current date) that are provided automatically [2] obsolete: ARCHETYPE-56 Add more discussion about the archetype descriptor ARCHETYPE-102 Windows XP Configuration Error ARCHETYPE-42 Update the mojo archetype to be compliant with the plugin documentation standard ARCHETYPE-107 maven archetype missing dependency versions breaks archetype:create ARCHETYPE-46 maven-archetype-archetype archetype places archetype.xml in the wrong location ARCHETYPE-49 mvn archetype:create ARCHETYPE-55 Maven archetype plugin ignores system properties
