Details
Improvement
Open
Major
Description
The following works:
$> mvn archetype:generate -DarchetypeCatalog=local -Dgoals=antrun:run
But this has some major disadvantages:
- The configuration of the goal has to be defined in the final POM of the new project
- The user using the archetype has to know about the additional parameter
It would be a big imovement if the a creator of an archetype could define some additional goals to be executed after the creation of the new project. THe documentation for 'generate' tells this about the 'goals' parameter: 'Additional goals that can be specified by the user during the creation of the archetype'. But it does not tell how the creator could define additonal goals.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | genrate goal to execute additional goals from archetype pom | generate goal to execute additional goals from archetype pom |
| Fix Version/s | 2.x [ 17632 ] | |
| Affects Version/s | 2.0 [ 14604 ] | |
| Affects Version/s | 2.0-alpha-4 [ 14253 ] | |
| Affects Version/s | 2.1 [ 16795 ] |
glad to see some progress on this 
any timeline for 2.2 already available?
for the moment, I still need to ship 2.1 in a week or two
if there is sufficient people wanting to help on it, we should be able to continue working after the 2.1 release: knowing how you immediately gave feedback when I changed the issue is a good sign of interest, then ability to help testing
it's motivating
It would be very usefull, especially to run very nice goals like versions:update-parent or versions:use-latest-releases, It would keep from upgrading archetypes versions only to update other versions inside...Thanks