Overriding a profile's features to run (previously a @wip scenario)
#649 log list of features at debug level to match the expected output of override profile scenario
Merge pull request #649 from serixscorpio/profile-override

Overriding a profile's features to run (previously a @wip scenario)
Default to using local/git version of core.

This should make sure the build does not rely on the released version of
cucumber-ruby-core.

@mattwynne - can we lose the assertions.feature? Doesn't multi_test
handle this now, or can we move the responsibility there?
Support changes to core report api
Use the correct git url for core
Tag out assertions feature. Related #652.

These scenarios are brittle, and do not work well with cucumber moving
to a multi-gem architecture.

I wonder if we should consider pulling out support for different
test/assertion frameworks into separate gems?

/cc @mattwynne @tom025 @os97673
Merge remote-tracking branch 'origin/master' into exceptions-in-hooks

* origin/master:
  Tag out assertions feature. Related #652.
  Use the correct git url for core
  Support changes to core report api
  Default to using local/git version of core.
  #649 log list of features at debug level to match the expected output of override profile scenario
  Overriding a profile's features to run (previously a @wip scenario)

Conflicts:
	lib/cucumber/reports/legacy_formatter.rb