Introduced Request - an object, that handles route and it's actual parameters. Request also has handler associated. All requests are listed in a hierarchal manner in application global Routes object a-la Rails or Play! routes.conf In some simple cases Controller instance becomes unnecessary since one can handle request directly in inline handler provided. HtmlLayout for the request result is chosen from the nearest object, that has layout property defined.

The documentation is not yet updated.

Fixed compile failure. I am very inexperienced with Kotlin and only tinkering, so this may be a very non-idiomatic fix. I tried fixing it while maintaining the forEach construct, but the type decomposition just didn't seem to want to work.

I simplified startup scripts by moving most code from .bat and .sh into Java code. On top of it I also implemented a shared run configuration that starts kara debug server with the application

The only way to run/debug of kara is to use kara_dist artifact output, i.e. out/artifacts/kara_dist folder. Before that once need to make kara_dist artifact in IDEA

Meanwhile I switched TeamCity build to generate package with use of IDEA artifacts

I updated templates of modules generation to reflect changes I made for project packaging. There was a missing point in the readme to notice one should specify IDEA path variable to point to kara home I also added a small fix to make HTML views set content type to HTML

drop root module, updated VCS settings added fix crlf for kara and kara.bat files, reverted all modules output paths to IDEA-default move scripts to bin folder

There were configuration duplication in current setup. It looks like kara.bat and kara.sh scripts ware designed to work only for local environment, so in the packaged Kara nothing worked

I removed older artifacts (that were duplicated in build.xml) and created a set of new ones: kara-core, kara-exec, kara-dist and kara-dist-zip.

It would be easy to generate kara-{version}.zip with help of TeamCity by setting artifact publishing rule out/artifacts/kara_dist => kara-%build.number%.zip

I moved all .jar files into lib folder

It's easy to assume that full kara package is deployed to out\artifacts\kara_dist folder

This is the first step for a built-in dependency manager. At the moment implementation is based on Ivy and simply provides a kara command "dependencies", which uses /ivy.xml file to resolve dependencies into /lib folder.

This patch contains

• a fix for build.xml to use Ant feature instead of *nix system provided 'touch' utility, thus making project compile under Windows
• I made test project reuse project JDK
• I added a hint comment to the error that could happen if Kotlin annotations are not enabled

Think a runtime exception gives a bad impression that something is wrong with the app as opposed to incorrect usage, so replaced the exception with a simple println when not supplying any arguments.