Friends,
Following the recent refactoring that the Lift archetypes went though,
we have moved forward to the new archetype metadata format [1] for all
the archetypes.
So far, the JPA related archetypes were using the new metadata format
while the others (esp. lift-archetype-blank and lift-archetype-basic)
were still on the old format. Moving to the new metadata format helps
us keep things consistent, comply with Maven's recommendation and open
the archetypes up for additional future enhancements.
From now on, the recommended Maven goal to generate projects from
archetype is to use "archetype:generate" [2]. The currently deprecated
Maven goal "archetype:create" [3] would not work to give expected
result and thus is not recommended anymore.
Therefore, to generate project from the archetypes in the master you
would use a command of the form:
mvn archetype:generate \
-DarchetypeRepository=
http://scala-tools.org/repo-snapshots \
-DremoteRepositories=
http://scala-tools.org/repo-snapshots \
-DarchetypeGroupId=net.liftweb \
-DarchetypeArtifactId=lift-archetype-blank \
-DarchetypeVersion=1.1-SNAPSHOT \
-DgroupId=com.mypackage \
-DartifactId=myproject \
-Dversion=1.0-SNAPSHOT
Currently, the possible archetypeArtifactId are:
- lift-archetype-blank
- lift-archetype-basic
- lift-archetype-jpa-blank-single
- lift-archetype-jpa-blank
- lift-archetype-jpa-basic
If you create project interactively (default behavior), -DgroupId, -
DartifactId, -Dversion are optional. Maven would prompt for these
values (and some more) interactively.
On the other hand, if you are using a batch/shell script to generate
project non-interactively, you would need to add at least -DgroupId, -
DartifactId and additionally set -DinteractiveMode=false.
Cheers, Indrajit
References:
[1]
http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-metadata.html
[2]
http://maven.apache.org/plugins/maven-archetype-plugin/generate-mojo.html
[3]
http://maven.apache.org/plugins/maven-archetype-plugin/create-mojo.html