Use config-extend instead of node.extend

node.extend merges arrays, which is virtually never what we want for
merging config options:

```coffeescript
defaults:
  key: [ "1", "2", "3" ]
override:
  key: [ "a", "b" ]

extend(true, {}, defaults, override) #=>
```

What we want is recursive merging but arrays are overwritten, not
merged:

```coffeescript
defaults:
  key: [ "1", "2", "3" ]
override:
  key: [ "a", "b" ]

extend(true, {}, defaults, override) #=>
```

The first option is optional, just like every other extend library.
However, in this library, it defaults to true if omitted. I'm leaving it
in for clarity. (and in case we have to change extend libs again)
Merge pull request #103 from testdouble/config-extend

Use config-extend instead of node.extend
Use files config for 'dest' values
Add a couple keys for compiled templates, and minified js/css
upgrade jasmine-only
0.11.5
Merge remote-tracking branch 'origin/master'
0.11.6
Finally kill the configure task!

Pour a shot, @davemo
register the default task to an empty array. 
Leaving it undefined has unintended consequences
when running `lineman grunt` without a task.
Switch to grunt-contrib-watch
default to nospawn
Fixes #112
Merge pull request #113 from testdouble/adds-command-chaining

Adds command chaining
Print out help if the user only enters `lineman`
Implements a nifty `config` reader

This action is designed to facilitate scripting
lineman based on its configuration.

The first bit of usefulness will be to verify 
Sass is enabled before we go about installing
the bundler & sass gems in our heroku build path.
One can do that like this:

```
$ lineman config enableSass
false
```

This config will follow '.' properties in the app
config, and will even follow indexed subscripts 
(e.g. 'foo[1]')

```
$ lineman config watch.pages.files[1]
app/templates/homepage.us
```

Neat-o! cc/@jasonkarns @davemo @theotherzach
0.12.0
Fix the note in the readme

The [] seems to be problematic because it is a reserved syntax for links (AFAIK) so it cannot be bolded (seems so). I think that the note works good without the need of [].
adds js+css to the default pages template context 

This is strictly for backwards-compatibility. If
a user upgrades to the latest lineman from a project
that predates the unification of generated & dist
filenames for app.js & app.css, they'll see a super
confusing white screen. Just ran into this with a 
current user.
0.12.1