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)
- a scimpi archetype, that I think is designed as a "mix-in" for the
application archetype.
We also eventually will need archetype support for:
- wicket
- restful
- jpa
- junit
- bdd (concordion)
- groovydom
- etc. etc.
Would it not make more sense to have a single archetype with different
child modules for each of the viewers? That'd be easier to test for us,
and I think easier to explain for end-users ("just delete the bits you
don't need").
Opinions?
Dan
