RSpec2 hasn't finished being merged into the next or master branches yet, it's only in 2.6.next and 2.6.x. When I sent my email yesterday we were in the middle of that merge and I didn't think it would take as long as it has, but it should be done today and therefore in all the major development branches.
On Thu, Jan 6, 2011 at 2:30 AM, Stefan Schulte <[email protected]> wrote: > On Wed, Jan 05, 2011 at 03:14:51PM -0800, Matt Robinson wrote: >> We're upgrading Puppet to use RSpec2, so you'll need to install that >> version of the gem if you don't already have it in order to run the >> specs. The main motivation for us was that RSpec2 has an option >> --fail-fast that you can use to end the spec run as soon as it >> encounters a failure. >> > > Should I be able to run the specs with RSpec2 right now? Because I > cannot (RSpec 2.0.0_beta22 - newest in gentoo portage) > > (branch next)% rspec spec/unit/type/host_spec.rb > ***************************************************************** > DEPRECATION WARNING: you are using deprecated behaviour that will > be removed from rspec-2.0.0. > > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/configuration_options.rb:69:in > `parse_local_options' > > * spec/spec.opts is deprecated. > * please use ./.rspec or ~/.rspec instead. > ***************************************************************** > /usr/lib64/ruby/1.8/optparse.rb:1450:in `complete': invalid option: --loadby > (OptionParser::InvalidOption) > from /usr/lib64/ruby/1.8/optparse.rb:1448:in `catch' > from /usr/lib64/ruby/1.8/optparse.rb:1448:in `complete' > from /usr/lib64/ruby/1.8/optparse.rb:1261:in `parse_in_order' > from /usr/lib64/ruby/1.8/optparse.rb:1254:in `catch' > from /usr/lib64/ruby/1.8/optparse.rb:1254:in `parse_in_order' > from /usr/lib64/ruby/1.8/optparse.rb:1248:in `order!' > from /usr/lib64/ruby/1.8/optparse.rb:1339:in `permute!' > from /usr/lib64/ruby/1.8/optparse.rb:1360:in `parse!' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/option_parser.rb:17:in > `parse!' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/option_parser.rb:4:in > `parse' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/configuration_options.rb:77:in > `parse_options_file' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/configuration_options.rb:69:in > `parse_local_options' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/configuration_options.rb:46:in > `parse_options' > from > /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/lib/rspec/core/runner.rb:22:in > `run' > from /usr/lib64/ruby/gems/1.8/gems/rspec-core-2.0.0.beta.22/bin/rspec:3 > from /usr/bin/rspec:8:in `load' > from /usr/bin/rspec:8 > >> Also, we noticed that there's a Rakefile in the spec directory that >> creates a bunch of rake tasks for every directory in spec. Is anyone >> using this or care about it? We didn't upgrade it to work with RSpec2 >> because we just noticed it and were hoping we could delete it. > > No I dont care. Havent even noticed it. >> >> Matt > > -Stefan > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
