Remove debug log messages from ScalatraTests

Removed debug log messages from ScalatraTests. These debug messages
do not add much value to the user and, if the user has debug level
enabled, will result in quite messy test output. In some cases,
such as when handling binary data, these messages even cause
iTerm 2 to crash.
Merge pull request #190 from mnylen/remove-log-debug-in-scalatratests

Remove debug log messages from ScalatraTests
Merge pull request #191 from dozed/develop

Chopping off ;
Use regular POST/PUT when using post/put overloaded with empty files and params

Fix a small issue using post/put overloaded with the files map
in ScalatraTests. Whenever the user would use the overloaded
method and provide empty files map AND params map, it would
generate a multipart/form-data request with empty body.

This causes a problem with Jetty, which throws IOException with message
"Missing initial multi part boundary" whenever it tries to parse a
multipart request with zero parts, and thus indeed, a one not having
the initial boundary.

The changes in this commit fix the issue by handling the special
case of params.isEmpty && files.isEmpty by falling back to regular
submit unless the user explicitly specified "multipart/form-data"
for Content-Type header.

Having this change enables users to do something like this
without needing any special handling from their part:

  def changeAvatar[A](userId: Int = 123, file: File = defaultFile)(f: => A): A = {
    put("/users/" + userId + "/avatar",
      Map[String, String](),
      (file != null) Map("file" -> file) else Map[String, File]()) { f }
  }

  test("user can change avatar") {
    changeAvatar {
      assert(user avatar has changed)
    }
  }

  test("changing avatar without providing file fails") {
    changeAvatar(file = null) {
      assert(avatar was not changed)
      assert(status === 400)
    }
  }
Merge pull request #192 from mnylen/fix-testhelpers-empty-map

Use regular POST/PUT when using post/put overloaded with empty files and...
Ditching link to old README, the book now wins.
Merge pull request #193 from futurechimp/develop

Ditching link to old README, the book now wins.
Initial (incomplete) attempt on fixing #148 - after filters run before the action in async actions

Still throws NPE whenever the action filter has route matchers.
Fix NPE with async after filters having a path matcher
Tabs to spaces
Simplified if clause for running after filters
Change the name request attribute containing the stored requestPath
Fix issue with contextPath getting set to null somewhere in async context for ScalatraFilters

Caches the value of requestPath and uses it on any subsequent calls to ScalatraFilter#requestPath
Merge pull request #194 from mnylen/issue-148-after-filter-async

Fix #148 - After filters in asynchronous requests
Force compilation to java6 compatible files.
Update to sbt 0.11.3, atmosphere to 1.0.0.beta1 and akka to 2.0.2
use right repository for ls-sbt
closes #195 Make liftjson support a single trait
* Replace JsonSupport with LiftJsonSupport or LiftJsonSupportWithoutFormats
* Replace LiftJsonRequestBody with LiftJsonSupport or LiftJsonSupportWithoutFormats
don't break apps existing users of the json integration
minor cleanup