Problem occurred for me running guard-jruby-rspec on windows.
We already autoload RSpec::Matchers to support folks using `RSpec::Matchers.define` before the normal time that rspec-core loads rspec-expectation (e.g. right before eval'ing the first example group block). This extends it to RSpec::Mocks and RSpec::Expectations for parity and to improve things for folks who we accidentally broke via this rspec gem change: rspec/rspec@f10bedd That was put in place to address rspec/rspec-mocks#359, which has more info.
…loaded to ensure we can programatically configure pattern
The most consistently tricky part to get right is the call site, so that's what this helper method helps with.
If RSpec is already loaded (it's common to do: ``` require 'rspec' # or 'rspec/core' require 'rspec/core/rake_task' ``` in a `Rakefile`), we can safely use the built in deprecation support however otherwise it's become to complicated to load the deprecation file alone so we drop back to a simplier warn.
…e check for listener understanding
The original spec was focused on the exact fix that was originally put in place, but we may wind up changing to an alternate fix that would not be tested by the spec as it was.
This reverts commit aef1c80.