BlueSpire/Durandal-Mimosa-Skeleton — pull request #15 by barkbarkuk (2014-12-08 14:19:59+00:00)
Title: Updated mimosa-config.coffee to use assets obtained through bower

I got a little confused when trying to get up to speed with mimosa and durandal because a number of the files under the assets/**/vendor folders seemed to come from the checked in mimosa skeleton rather than from the bower/mimosa mechanisms which I believe are supposed to put these in place.

The checked in mimosa-config.coffee resolves most of the bower issues seen when running `mimosa watch -C`

I modified the sample applications main.js to use bootstrap.js without the '-3.1.0' suffix as I don't believe it's needed unless multiple versions of bootstrap need to be included through bower.

The other modified files and deleted files are a direct result of changes to the mimosa-bower config after cleaning things up.
Should dependencies managed by mimosa and bower be checked in?