On 6/25/06, Mike Lundin <[EMAIL PROTECTED]> wrote:
Is there a way to have archetypes act cumulatively? It seems to me that it
would make sense that you would be able to run an archetype command multiple
times in a directory and still end up with only one pom and set of
directories. That way, what Wendy suggests below would work. If you have
Struts elements, you run the Struts archetype. Then, if you have Hibernate
or Spring, you can run that afterwards and still keep them in the same
project.
Am I misunderstanding the whole idea of an archetype when I think like this?
It seems to be one archetype == one module. If you're going to run it
multiple times, you create a parent pom, then do mvn archetype:create
a few times, and it *does* handle setting up the parent/child module
relationships.
My fear is that people will just do the webapp module, and never set
up the integration tests, so I tend to want to keep it all together.
AFAIK, the archetype plugin will not "overlay" an existing project,
for example to add more dependencies to a pom. It just complains that
the directory already exists.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
