first implementation of the ninja framework test
fixing the persistence config. By default, use the container datasource
dao refactor
enabling the 'production' mode
testing the standalone version with the fat-jar
Pyramid benchmark for Python 2 and 3
Use create-postgres.sql
Merge branch 'master' into ninja
upgrading to ninja 2.1.0
Merge branch 'master' into ninja
fixing the setup.py file: start & stop have the required arguments and all the subprocess calls route the stderr & stdout as required
removing the linked folders
fixing the ninja-standalone setup
fixing the source path
Fix the Sinatra tests to more closely resemble production settings

This commit makes 3 changes to the Sinatra application that more
closely resembles what someone would use in production (if throughput
is a concern) and should improve performance on both JRuby and Ruby.

* We disable Sinatra's static file serving so it doesn't waste time on
each request looking for static files, since we have none. In
production this is usually handled by a frontend server anyway.

* We specify which JSON encoder to use so that sinatra/json doesn't
try several options on each request until it finds one it can use.

* We disable the per-request connection pooling in
sinatra/activerecord and instead use ActiveRecord's with_connection to
explicitly control connections. The default behavior is overly
simplistic and incurs expensive synchronized method calls on every
request, even if the request doesn't touch the database.

This change makes the non-database routes several times faster, and
should improve the performance of the database route a bit less.
Fix typos
Use the same version of Jackson for JSON tests

As discussed at https://groups.google.com/forum/#!topic/framework-benchmarks/WM9k_hwkhLQ
PR #640 Remove newly added jetty-maven-plugin.

Its purpose was to run the app as a smoke test to verify it is not broken.
But it doesn't work atm.
Update source_code
removing the linked META-INF folder