Hervé BOUTEMY wrote: > > Forwarding this question to dev list... >
Yay! I have the attention of the right person at the right time. Hervé BOUTEMY wrote: > > archetype descriptor [2] should have goals > I'll dump related thoughts here: * I like the ability to add goals in archetype descriptor * sometimes certain goals will always have to be executed after an archetype, why not allow it to be done automatically, less instructions for the archetype consumers to follow * It cleanly augments the velocity templating with custom logic * I use one-off Groovy+AntDSL mojos in my highly-specialized archetypes to "continue the conversation" started by archetype, I need the boost of logic to really add value to the archetype * My follow-up goals have interactivity in CLI, not sure how m2e would handle that in its wizard * the goals need to allow properties (e.g. "<goal>doit -DmyProperty=true</goal>) * goals need to execute in order, currently I don't think order is respected with the catalog descriptor method and somewhat-related: * archetype has some default properties (package, artifactId), which is nice, but it is hard to override and/or not use them, e.g. if I add a "package" property, it shows up twice in the list displayed to user -- View this message in context: http://maven.40175.n5.nabble.com/Fwd-archetype-catalog-xml-and-its-properties-and-goals-elements-what-populates-them-tp2843289p2843788.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
