#238
- Created on2009-12-13 15:57
- Reported by
- StatusAccepted
- PriorityNormal (3)
- Assigned to
- Milestone-
- Plan Level-
- Due Date-
Have minimal support for archetype:create telling user to use archetype:generate instead
Quoting from committers call notes:
David suggested
that archetype:create remain supported but generate a project that
essentially tells the user to use archetype:generate instead. Perhaps
instead of generating a full Maven app. Thought that occurred to me
(Kris) after the call: instead we could just generate a directory with
a single README that instructs the user to use maven
archetype:generate instead?
Need to explore the possibility.
David suggested
that archetype:create remain supported but generate a project that
essentially tells the user to use archetype:generate instead. Perhaps
instead of generating a full Maven app. Thought that occurred to me
(Kris) after the call: instead we could just generate a directory with
a single README that instructs the user to use maven
archetype:generate instead?
Need to explore the possibility.
Leave a comment
on 2010-02-19 03:07 *
By Indrajit Raychaudhuri
(from github) See the "Goals Overview" section in http://maven.apache.org/plugins/maven-archetype-plugin/index.html for the difference.
Unfortunately, archetype:create doesn't provide any mechanism to display instruction when the goal is executed.
Unfortunately, archetype:create doesn't provide any mechanism to display instruction when the goal is executed.
(from ngocdaothanh on github) What's the different between archetype:create and archetype:generate? Why not only display some instructions on the screen? "generate a directory with a single README" is ridiculous, the user will remove the directory anyway. Is the README long?