Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

o adding a note to share with a couple other people 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@326919 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2005-10-20 15:00:35 +00:00
parent 3b0bb4c11c
commit 8f85a92cfd
1 changed files with 85 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

85
maven-archetype/archetype-model.xml Normal file
View File

@ -0,0 +1,85 @@
<archetype>
<id>quickstart</id>
<fileSets>
<!--
o filtering
o arbitrary directories even if it to make the job easier internally. we
really don't want people making any sort of directory structure they
want.
o a tool to create archetypes easily
<plugin>
<id>maven-archetype-plugin</id>
<executions>
<execution>
<goals>
<goal>bundle</goal>
</goals>
</execution>
<configuration>
How do we want to configure this?
o directory tree of archetypes?
o one archetype per project?
<descriptor>src/main/archetype/archetype.xml</descriptor>
</configuration>
</executions>
</plugin>
o need to specify parameters and metadata about parameters
- pluggable validation type/group
- localized descriptions
o any ideas to take from the IDEA template mechanism that uses velocity
-->
<!-- Project application sources -->
<fileSet>
<directory>src/main/java</directory>
<filtering>true</filtering>
</fileSet>
<!-- Project application resources -->
<fileSet>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</fileSet>
<!-- Project test sources -->
<fileSet>
<directory>src/test/java</directory>
<filtering>true</filtering>
</fileSet>
<!-- Project test resources -->
<fileSet>
<directory>src/test/resources</directory>
<filtering>true</filtering>
</fileSet>
<!-- Project site -->
<fileSet>
<directory>src/site</directory>
<filtering>true</filtering>
</fileSet>
</fileSets>
<!-- So we'll collect these parameters and feed them into the velocity context -->
<parameters>
<parameter>
<name></name>
<type></type>
<required></requrired>
<!-- This will get farmed out to a resource bundle -->
<descriptionKey></descriptionKey>
</parameter>
</parameters>
</archetype>