Add http-proxy generator/blueprint
setup proxies with http-proxy
Add http-proxy as a dependecy in case someone uses proxies
Rename Addon's _root to root
Merge pull request #1537 from bcardarella/bc-addon-root

Rename Addon's _root to root
Recursive addons
Merge pull request #1509 from bcardarella/bc-addons-in-your-addons

Recursive addons
update testem version, enables api proxy in testing
Merge pull request #1539 from ghedamat/mattia/update-testem-deps

update testem version, enables api proxy in testing
Update app blueprint bower.json to use latest ember-resolver
Merge pull request #1540 from jdjkelly/master

Update app blueprint bower.json to use latest ember-resolver
Update loader.js to 1.0.1
Merge pull request #1543 from abuiles/bump-loaders.js

Update loader.js to 1.0.1
Ensure non `/assets/` files can be served.

Previously, any files in `public/` (outside of `public/assets/`) would
not be served up as it was assumed to match history API requests and
redirect to `/index.html`.

This commit fixes that, by serving up any files that exist in the built
output directory before falling back to checking for history API support
(and subsequently proxying).
Merge pull request #1549 from rwjblue/fix-public-dir

Ensure non `/assets/` files can be served.
Add CHANGELOG entry for #1549.
Include robots.txt and crossdomain.xml.
Merge pull request #1550 from rwjblue/html5-boilerplate

Include robots.txt and crossdomain.xml.
[WIP] es6 namespaced addons

This will allow one to have modules in their addons that are namespaced
under their addon's name rather than the application's namespace.
Expects the following directory structures:

addon
└── mixins
    └── data-route.js
app
└── controllers
    └── people.js
Any modules in app/ will always be namespaced under whatever namespace
the parent application has. This allows the addon developer to create
common-sense defaults that get pulled into the application then can be
overridden by the consuming developer in the parent project's app/
directory.

Any modules in addon/ will always be namespaced under the addon's name.
This name is always forced to lower-cased & hyphenated. So:

"Ember CLI Some Addon" => "ember-cli-some-addon"
Then in whichever modules the consuming developer wants to use this
module they can do:

import DataRouteMixin from "ember-cli-some-addon/mixins/data-route";
This feature will traverse the addon/ directory and build a list of
modules from the available file names and merge this into
app.importWhitelist after the addon's modules have been compiled to ES6.

This feature will compile the addon's assets into vendor.js and
vendor.css. It does this by expecting the addon to compile its own
assets into a single file then all addon's files are concat'ed into an
addon.js then eventually concat'ed into vendor.js.

The EmberApp's registry is no passed into all preprocessors. This allows
the Addon to manage its own registry rather than rely on the private singleton.
Merge pull request #1544 from bcardarella/bc-namespaced-addons

[WIP] es6 namespaced addons