Fixed RequireJS path for compilation in production mode in windows
Fixed RequireJS path for compilation in production mode in windows
Optimize templates. fixes #2033.

Use a single StringBuilder for building template output (as opposed to many string builders appending each other up the tree).
Don't create collections for single items in template source.
Change Appendable's definition to support single StringBuilder.
Ignore resource directories when trying to loadMessages in MessagesPlugin, otherwise app don't start if there's a matching directory
Ensure byte code enhancer updates incremental compiler analysis

In SBT 0.13.1, a feature was added to the incremental compiler that
meant that products (class files) were invalidated if their modification
date changed, where previously the only check that was done was whether
they existed.

Play's byte code enhancement enhances Scala template classes, and this
enhancement was updating the modification date, naturally causing the
incremental compiler to invalidate the classes on its next run, and
recompiling them unnecessarily.

This change updates the analysis object after Play has modified any
template files, and then writes the updated analysis out to disk.
Typo in Cache.scala ScalaDoc
remove unnecessary exec ctx prep from Iteratee.flatMap

commit 2b276d24 implemented the lines:
```
case Step.Done(a, Input.Empty) => executeIteratee(f(a))(ec /* still on same thread; let executeIteratee do preparation */ )
case Step.Done(a, e) => executeIteratee(f(a))(ec.prepare /* still on same thread; let executeIteratee do preparation */ ).pureFlatFold {
```
However, the `ec.prepare` is incongruous with the adjacent comment, and the preparation is definitely not required as the preparation is indeed handled by `executeIteratee`.
Further fixes with respect to issue #2256
Merge pull request #2237 from jroper/enhancer-analysis-update

Ensure byte code enhancer updates incremental compiler analysis
Merge pull request #2247 from fernandoacorreia/cache-orelse

Typo in Cache.scala ScalaDoc
Etag => ETag

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.19
Merge pull request #2260 from sclasen/patch-1

Etag => ETag
Fix for Java Message Arguments handling

There was a bug in the handling of message arguments when used in Java.

I discovered it when using `@Constraints` annotation on my model objects and returning the validation errors as Json. This simple example illustrate the bug :

     //in my model object
     @Constraints.MinLength(2)
     public String myField;

     //in my controller (Json version)
     return badRequest(form.errorsAsJson()); //"Minimum length is [2]"
     //in my controller (form render)
     return badRequest(formView.render(form)); //"Minimum length is 2"

 By digging into the code I found out that we were passing directly a List to `Messages.get()`, which in turns rewrap it into another `List` to then call the API. The bug is in fact wider than I first thought and the use case I described must not be the only one where we get this kind of error.

 The patch is simple, it checks if there is only one argument and if it is a `List`, in this case it returns the `List` as is, otherwise the previous behavior is kept (wrapping with `Arrays.asList`).
 Tests were added in MessagesSpec to validate the behavior in Java, and a MessagesTest class was added to check the behavior of the arguments transformation.

 CLA has been signed.
Fix typo
Updated IntelliJ setup with missing step

Clarified steps to setup IntelliJ by adding in missing step.
Add missing import to docs
Add play.plugins file with comments to integrationtest
Merge pull request #2122 from bischak/master

Fixed RequireJS path for compilation in production mode in windows
Merge pull request #2268 from matthew-lucidchart/pullrequest-template-optimizations

Optimize templates. fixes #2033.
Scaladoc and specs for SQL statement parser