Fixes incompatibility with RSpec 3.0.0

[treydock]

• Pin rspec dependency to < 3.0.0 Fixes RSpec 3.0.0 breaks rspec-puppet #200
• Fix deprecation warnings related to 'display_name', fixes rspec3 breaks rspec-puppet - undefined method `display_name' for RSpec::ExampleGroups #198

Same solution as #199 but also pins rspec-puppet to RSpec < 3.0.0 as there are likely numerous other issues people will face when depending on rspec-puppet to pull in the necessary rspec dependencies.

[030]

I have cloned the repo, implemented your changes, built and installed the gem and now the rspec tests work again. Thank you.

sudo rspec
...

Finished in 0.25638 seconds
3 examples, 0 failures

Total resources: 3
Touched resources: 3
Resource coverage: 100.00%

[doc75]

When I use this version, the bundle update install rspec version 3.0.0.rc1 and it still break.
Anyone knowing a way to force really a version lower to 3.0 (even rc) ?

[hunner]

I don't think rspec-puppet depends on rspec 2, does it?

If your rspec-puppet test use rspec 2 syntax, then you should be pinning to rspec 2.

[hunner]

@doc75 You can add a Gemfile to your module's path and use bundler to use rspec 2. Your Gemfile should list gem 'rspec-puppet' and gem 'rspec', '~> 2.0' to get rspec 2, and then bundle install && bundle exec rake spec

[doc75]

@hunner: You are right. But indeed, I did not force my test to use RSpec2 and that it why this pull request does not force it either as it takes 3.0.0.rc1
I could have forced my test to use only RSpec2, but the effort to move to RSpec3 was quite low in my case.

BTW, I created PR #204 to make rspec-puppet compliant with RSpec3.
0