fix pattern for variable parts of route to handle multiple regex parts

currently only one part *with regex* can be specified in a route
making variable part regex pattern reluctant gives possibility to specify
more than one variable parts with regex
Merge branch 'develop' into multiple-regex-route
add changelog and own name in team.md
Revise the boolean setting controlling external configuration hot-reloading

The addition of the setting within the external application.conf file to control
enabling/disabling runtime hot-reloading for #235 was hastily done.

In retrospect, it would be better to control this behavior by use of a System
property which complements the system property already used to specify the
external configuration location.

    java -Dninja.external.reload=true -Dninja.external.configuration=app.conf
Merge pull request #238 from gitblit/hotreload2

Revise the boolean setting controlling external configuration hot-reloading
Added test for NinjaCache.
Merge branch 'develop' of github.com:ninjaframework/ninja into develop
Merge branch 'develop' into bazi-multiple-regex-route

Conflicts:
	ninja-core/src/site/markdown/developer/changelog.md
Merge branch 'bazi-multiple-regex-route' into develop
Removed localized lookup in Freemarker templates. Not needed as Ninja does i18n already
Stability improvement for Jpa blog archetype - setup works now in a predictable manner for testcases (ra)
update routing docs to reflect changes in PR #236

routes can have multiple regex parts
Merge pull request #240 from bazi/docs/pr-236

Update routing docs to reflect changes in PR #236
Implement a Ninja Metrics module

Applications will need to be manually instrumented by:

1. Adding the optional ninja-metrics dependency
2. Installing the MetricsModule in their conf.Module class
3. Subclassing InstrumentedNinja in their conf.Ninja class
4. Applications may optionally instrument their NinjaCache

Ninja-Metrics will collect data on controller methods annotated
as @Metered or @Timed.  Non-annotated controller methods are
largely ignored except for general count collection.

InstrumentedNinja will monitor bad requests, internal server errors,
and routes not found. It will also keep a real-time count of active
requests.

To try this out:

1. `mvn install` in the repository root
2. `mvn ninja:run` in the ninja-servlet-integration-test
3. Startup VisualVM
4. Install the MBeans plugin through the Tools->Plugins  menu
5. Drill into the NinjaJetty instance listed in VisualVM and select the *MBeans* tab
6. Browse the test app and click on the different available *ninja.cache* and *ninja.requests* metrics
Added interceptors to measure everything (™).
More cleanup for metrics.
Some potential code refinments.
Some more improvements for Metrics.
Fixed problem with wrong source level. Now fixed to 1.7.
Reduce to one metric registry, specify ninja.* names, setup JMX with app name