Fix an exception when the DeprecationFormatter is initialized with an IO stream that doesn't respond to :path.
Merge pull request #1757 from GoBoundless/undefined_method_path_master

Fix an exception when the DeprecationFormatter is initialized with an IO stream that doesn't respond to :path.
changelog for #1757
[skip ci]
Also document around/exception behavior.
Merge pull request #1772 from jkingdon/around-and-exception

Also document around/exception behavior.
Changelog for #1772
[skip ci]
Updated travis build scripts (from rspec-dev)
Use 1.8.7 compatible ruby syntax.
Satisfy rubocop.

Offenses:

lib/rspec/core/example.rb:418:11: C: Do not prefix reader method names with get_.
      def get_generated_description
          ^^^^^^^^^^^^^^^^^^^^^^^^^
lib/rspec/core/example.rb:421:131: C: Line is too long. [139/130]
        location_description + " (Got an error when generating description from matcher: #{e.class}: #{e.message} -- #{e.backtrace.first})"
                                                                                                                                  ^^^^^^^^^
Fix invalid YARD method reference.

[warn]: In file `lib/rspec/core/formatters/protocol.rb':3: Cannot resolve link to #dump_failure from text:
[warn]: ...{#dump_failure}...
Fix YARD warnings.

[warn]: In file `lib/rspec/core/rake_task.rb':29: Cannot resolve link to ,// from text:
[warn]: ...{,//}...
[warn]: In file `lib/rspec/core/rake_task.rb':29: Cannot resolve link to ,// from text:
[warn]: ...{,//}...

Note that I haven't been able to repro these warnings locally with YARD
but they happen on travis. While I was at it, I fixed up some
inaccuracies in the documented defaults for rake task options.
Merge pull request #1778 from rspec/update-travis-build-scripts-2014-11-12-for-master

Updates from rspec-dev (2014-11-12)