I would say, judging by my earlier feelings, that I prefer a single archetype.
I would add a proviso, though: unless there is a way to add functionality to an existing project using an archetype, the archetypes should be "themed". [I don't think I'd like a single archetype that has all possible options would be a good idea... ;)] If this is not possible, then having the option to "delete the bits you don't want" is a good compromise. > Currently we have: > - an exploration archetype (a single module, combining dom, fixture, > service) > - an application archetype (a multi-module with separate projects for > dom, fixture, service, commandline) What opinions to you all have here: do you prefer a single module per application, or multiple projects? Practically, which "works better" in your experience? A single project certainly reduces the "link effort" on maven - at the moment I have to install all projects before I can run scimpi, for example. Regards, Kevin
