Added the bulk copy to remote resources
Added test for the normal copy methods on a remote resource
Fix #379

That's an error I made in my `env` refactoring
Update Base.tarball test so it don't rely on network
v0.14.0-rc.1
Add/rewrite unit tests, fix some doc strings
Change env#error to returns the Error object

env#error was returning Self, and this was misleading other part of
the application in thinking no error had been thrown when an error
listener was set. Now env#error returns the provided error for more
consistency and to allow other part of the system to handle errors.
Clone arguments passed to env#create generators.

Add and refactor lots of related unit tests.
Extract the path resolution logic out of .register. Refactor paths handling in the test/env.js
Merge pull request #380 from SBoudrias/refactor-env

Env refactoring
Merge pull request #382 from SBoudrias/fetch-tests

Update Base.tarball test so it don't rely on network
Re-add `fetch.request` to ensure backward compatibility (Fix #387)
Update to chalk 0.3
Fix actions test on windows
Merge remote-tracking branch 'wesleytodd/remote-bulk-copy'

Conflicts:
	test/actions.js
Adds support for generator resolving when yeoman-generator has been linked

Fixes #334
Merge pull request #394 from pull-requests/fix-module-resolving

Adds support for resolving when yeoman-generator has been linked
Extract the env resolver
Extract storing logic from the environment
Remove env.engine and env.remote

env.engine isn't used anywhere in the code and doesn't make much sense as
generator themselve select which engine to use, not the runner.

env.remote was supposedly used to fetch local generator, but the logic
doesn't work. It runned an async task and continued to simply launch error.
My guess is env.remote is an old relicat from a deprecated feature.