概括图很形象，来自https://maven.apache.org/archetype/maven-archetype-plugin/index.html
1.从工程创建原型
mvn archetype:create-from-project
如果需要参数定制化
https://maven.apache.org/archetype/maven-archetype-plugin/examples/create-with-property-file.html
2.进入/target/generated-sources/archetype目录
find ./ -name target |xargs rm -rf 删除自动生成的target
find ./ -name \.\*|grep src|xargs rm -rf 删除.开头的文件
mvn clean install/deploy
安装archetype到本地仓库
archetype安装的地址是在maven安装目录下面的conf/settings.xml文件中指定的(字节)。
默认会在 ~/.m2 目录下面生成一个archetype-catalog.xml文件（和默认的settings.xml在同一个目录
3.Eclipse创建maven项目过程中，选择的“Default Local”指向的地址就是 ~/.m2，
所以文件archetype-catalog.xml会被eclipse自动读取，使用eclipse创建maven项目的时候可以在”Default Local”一项中找到刚才自定义archetype名字。
当eclipse的maven设置中，User Settings选择的settings.xml指向的本地仓库地址和maven安装目录下的那个settings.xml中指向路径一样的时候，eclipse才能读取得到刚才安装的自定义的archetype的源文件，这样eclipse才能复制源文件并创建项目。
4.卸载安装的archetype，将~/.m2目录下面的archetype-catalog.xml文件中对应的字节段删掉，并且把本地仓库中相应groupId和artifactId下面的文件删掉
5.安装到本地仓库中的archetype只可以被自己使用，如果想要共享，那么必须deploy到内部maven仓库中
6.如果想要生成项目，列出所有的archetype, mvn archetype:generate ；只列出本地archetype，mvn archetype:generate -DarchetypeCatalog=local，
筛选archetype，后面必须加“:”，可以只显示某个groupId下面的archetype
mvn archetype:generate -Dfilter=com.glowd.arch:
7.如果使用的是maven-archetype-plugin 2.4,可以直接在命令行生成archetype工程，不需要进入交互模式，但是最新版的maven已经不支持了，基于安全考虑
mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=http://nexus.glowd.com:1998/nexus/content/repositories/releases/com/glowd/sample/sample-archetype/0.0.1/sample-archetype-0.0.1.pom
8.mvn archetype:crawl
扫描整个~/.m2/repository/，将扫描到的所有的archetype进行排序更新，在我们执行mvn archetype:generate -DarchetypeCatalog=local时能够看到所有整理过后的扫描项，
扫描的内容在~/.m2/repository/archetype-catalog.xml中
9.Testing
The user can provide archetype test projects by placing them in src/it/projects folder of their project. Upon creating archetype from the existing project all the test projects will be executed to verify the archetype created by this project is good. Read more about testing maven archetype.
具体参考https://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html
10.Configuration
The create-from-project goal enable the user to provide some sensible configuration using the system properties or a property file.
The system properties permits the user to define the groupId, artifactId, version of the created archetype. They also permits to override the resolved package and to create a partial archetype.
When used, the property file takes precedence over the system properties. It is also the only way to define additional properties in the archetype.
具体参考https://maven.apache.org/archetype/maven-archetype-plugin/examples/create-with-property-file.html
10.Post-generation script
If the user wants to customize the generated project even further, a groovy script named archetype-post-generate.groovy can be added in src/main/resources/META-INF/. This script will end up in the generated archetype’s META-INF folder and will be executed upon creating a project from this archetype. This groovy script has access to the ArchetypeGenerationRequest object, as well as all the System.getProperties() and all the archetype generation properties the user has specified.
