archetype-catalog.xml[1] has support for adding properties and goals I'm especially interested in the goals portion. I have some setup logic that should always be executed after archetype creation. If I manually create the archetype-catalog.xml file and add goals, the archetype:generate CLI interface does recognize and run the goals after project creation (m2e does not, unfortunately).
How do goals normally get inserted into the archetype-catalog file? Is that a manual process? <goals> are neither in the old[2] nor new[3] archetype descriptors. How does that work if the Nexus plugin [4] is handling the catalog file? The properties part makes a little more sense, because <requiredProperties> is in the archetype metadata file, so I can see where it might come from. (although none of the archetypes listed in central have properties in the main catalog file[5], so that also is broken in m2e because m2e does not "see" the the non-standard properties until the archetype is locally installed, which does not happen until after the "set properties" wizard page, by then it's too late) Any insights? [1] http://maven.apache.org/archetype/archetype-common/archetype-catalog.html [2] http://maven.apache.org/archetype/archetype-common/archetype.html [3] http://maven.apache.org/archetype/archetype-common/archetype-descriptor.html [4] https://docs.sonatype.org/display/Nexus/Nexus+Archetype+Plugin [5] http://repo1.maven.org/maven2/archetype-catalog.xml --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
