This stuff has pretty much been implemented in 0.1.0-incubating
Plan
Our plan is to support just a single archetype, *quickstart. This will generate a multi-module project with separate modules for all of the main components.
The modules generated by the archetypes will be:
|
|
Description |
Notes |
---|---|---|---|
app/ |
|
Parent |
|
|
dom/ |
Domain object model, depends on applib only |
|
|
domsvc/ |
Domain services (not repositories) |
|
|
fixture/ |
Fixtures to setup object store |
|
|
quickrun/ |
Quick run of DnD and HTML viewers; includes JUnit tests |
Currently called 'cmdline' |
|
objstore-default/ |
Repository implementations for default object store |
Currently the repositories in 'service' |
|
objstore-sql/ |
Repository implementations for SQL object store |
... if that makes sense |
|
objstore-nosql/ |
Repository implementations for NoSQL object store |
... if that makes sense |
|
remoting-dnd-http/ |
Run and jar packaging up DnD viewer (as client over http protocol) |
|
|
remoting-server-http/ |
Run and webapp packaging for server-side remoting (over http protocol) |
|
|
viewer-dnd/ |
Run and jar packaging of DnD (as standalone) |
|
|
viewer-html/ |
Run and webapp packaging of HTML viewer |
|
|
viewer-restful/ |
Run and webapp packaging of Restful viewer |
|
|
viewer-scimpi/ |
Run and webapp packaging of Scimpi viewer |
|
|
viewer-wicket/ |
Run and webapp packaging of Wicket viewer |
|
|
tests-unit/ |
Unit tests (Junit viewer) |
|
|
tests-bdd/ |
BDD tests (Concordion) |
|
Creation
Since this is a large archetype, the intention is to reverse generate the archetype from a running protoype. This will make the debug process easier. See RecreatingMavenArchetypeFromProject for more details.