maven archetype for kauri-module

[mpo]

To help creating new modules it makes sense to be able to start such development using maven archetypes.

[mpo]

This feature is introduced in 0.3 already. I'm listing here a number of possible future enhancements to the current approach.

• fixed 'module1' creation: would be better if the name of the module(s) to be created can be configured or specified during archetype-execution
• the current embedded modules aren't yet following the new name-conventions introduced in the samples (see #117). e.g.
  • still uses 'resources' not 'static'
  • still -Module suffixes in kauri.xml
  • still old bean-names in <kauri:modules>
  • spring/services.xml
  • still exports 'router', not 'main' service
• fixed links in the index.xml of basic should be prefixed with by ${publicUri('service:/main')} to allow non default mount points
• in general the added stuff in the archetypes could use more comments to explain the constructs. (maybe by refering to online docs)

[mpo]

The wrappig kauri-project-template.sh script could be inrtoducing the -q option to maven.

This silences the current list of [warnings] coming from the use of various ${version.*} properties in the artefact.

[mpo]

to tackle together with #173

[mpo]

r1615 and r1616 got rid of the module1 reference

[karel]

All the above suggestions have been applied.
Adding 'test the archetype' instructions to the build instructions.