PepsRyuu/lamda — pull request #2 by Dremora (2014-03-24 04:51:38+00:00)
Title: Build automation for Lamda

* Lamda only (no optimizer)
* Using **gulp** as the the only JS build tool which does it right ;) In order to install it, type ```npm install -g gulp``` followed by ```npm install```. Type ```gulp``` to start the build.
* Source is minified using **uglify**, both minified and uncompressed version are copied to ```dist/``` folder (a common practice for client-side packages).
* Tests are run in **Karma** test runner. I didn't change the tests, but all JavaScript had to be split into a separate file in order to run in Karma. I've also modified ```assertEquals``` function to throw exception when assertion fails. Probably needs to be replaced with a proper assertion library.
* Added .travis.yml file for running the build on Travis CI. Unfortunately, the build is failing now due to a bug in text plugin (files are requested with double slash in path, which might confuse some web servers). Go to https://travis-ci.org , log in using GitHub, import all our projects - it will do the rest for you. No need to create a build job, .travis.yml will be picked up automatically. Isn't this cool? :)

Ideally this project needs to be split into lamda and lamda-optimizer to properly utilize Travis. It expects to see only a single build job description in the git root, and it's going to be quite tricky to make it work with two independent projects in one repo.