Usage

For information how to include the plugin in your build configuration, see the project's README.

Directory Structure

This plugin uses it's own source folder and a specific structure underneath:

/
|- src
   |- main
      |- emberjs
         |- libs
         |- js
         |- templates

All your external libraries like JQuery or Ember.js are going into the libs folder. They might contain versioning information but you should not use minified versions to ease debugging. The plugin will minify the sources when aggregating them (the feature is not implemented yet).

Use the js folder for your application's javascript and the templates folder for your handlebars templates. You have to name each template with *.handlebars suffix otherwise they are not picked up by the plugin. This part might be configurable in a future version of the plugin.

Running the plugin

The plugin is run each time you run compile on your project. This does also work very nicely in conjunction with the fabulous SBT Revolver Plugin for fast development turnarounds, in fact this runs way faster than the ruby based bpm tool. The aggegated output is generated in

/
|- target
   |- scala-2.9.1
      |- resource_managed
         |- main
            |- assets
               |- application.js

This location and the filename is not configurable but this will change in a future version of the plugin. If you use Ember.js with spray you should serve either the entire assets folder as a resource directory or just the application.js file.