vim-jar 0.0.1

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/History.markdown

@@ -0,0 +1,104 @@
+## rspec-core release history (incomplete)
+
+### 2.1.0 / 2010-11-07
+
+[full changelog](http://github.com/rspec/rspec-core/compare/v2.0.1...v2.1.0)
+
+* Enhancments
+  * Add skip_bundler option to rake task to tell rake task to ignore the
+    presence of a Gemfile (jfelchner)
+  * Add gemfile option to rake task to tell rake task what Gemfile to look
+    for (defaults to 'Gemfile')
+  * Allow passing caller trace into Metadata to support extensions (Glenn
+    Vanderburg)
+  * Add deprecation warning for Spec::Runner.configure to aid upgrade from
+    RSpec-1
+  * Add deprecated Spec::Rake::SpecTask to aid upgrade from RSpec-1
+  * Add 'autospec' command with helpful message to aid upgrade from RSpec-1
+  * Add support for filtering with tags on CLI (Lailson Bandeira)
+  * Add a helpful message about RUBYOPT when require fails in bin/rspec
+    (slyphon)
+  * Add "-Ilib" to the default rcov options (Tianyi Cui)
+  * Make the expectation framework configurable (default rspec, of course)
+    (Justin Ko)
+  * Add 'pending' to be conditional (Myron Marston)
+  * Add explicit support for :if and :unless as metadata keys for conditional run
+    of examples (Myron Marston)
+  * Add --fail-fast command line option (Jeff Kreeftmeijer)
+
+* Bug fixes
+  * Eliminate stack overflow with "subject { self }"
+  * Require 'rspec/core' in the Raketask (ensures it required when running rcov)
+
+### 2.0.1 / 2010-10-18
+
+[full changelog](http://github.com/rspec/rspec-core/compare/v2.0.0...v2.0.1)
+
+* Bug fixes
+  * Restore color when using spork + autotest
+  * Pending examples without docstrings render the correct message (Josep M. Bach)
+  * Fixed bug where a failure in a spec file ending in anything but _spec.rb would
+    fail in a confusing way.
+  * Support backtrace lines from erb templates in html formatter (Alex Crichton)
+
+### 2.0.0 / 2010-10-10
+
+[full changelog](http://github.com/rspec/rspec-core/compare/v2.0.0.rc...v2.0.0)
+
+* RSpec-1 compatibility
+  * Rake task uses ENV["SPEC"] as file list if present
+
+* Bug fixes
+  * Bug Fix: optparse --out foo.txt (Leonardo Bessa)
+  * Suppress color codes for non-tty output (except autotest)
+
+### 2.0.0.rc / 2010-10-05
+
+[full changelog](http://github.com/rspec/rspec-core/compare/v2.0.0.beta.22...v2.0.0.rc)
+
+* Enhancements
+  * implicitly require unknown formatters so you don't have to require the
+    file explicitly on the commmand line (Michael Grosser)
+  * add --out/-o option to assign output target
+  * added fail_fast configuration option to abort on first failure
+  * support a Hash subject (its([:key]) { should == value }) (Josep M. Bach)
+
+* Bug fixes
+  * Explicitly require rspec version to fix broken rdoc task (Hans de Graaff)
+  * Ignore backtrace lines that come from other languages, like Java or
+    Javascript (Charles Lowell)
+  * Rake task now does what is expected when setting (or not setting)
+    fail_on_error and verbose
+  * Fix bug in which before/after(:all) hooks were running on excluded nested
+    groups (Myron Marston)
+  * Fix before(:all) error handling so that it fails examples in nested groups,
+    too (Myron Marston)
+
+### 2.0.0.beta.22 / 2010-09-12
+
+[full changelog](http://github.com/rspec/rspec-core/compare/v2.0.0.beta.20...v2.0.0.beta.22)
+
+* Enhancements
+  * removed at_exit hook
+  * CTRL-C stops the run (almost) immediately
+    * first it cleans things up by running the appropriate after(:all) and after(:suite) hooks
+    * then it reports on any examples that have already run
+  * cleaned up rake task
+    * generate correct task under variety of conditions
+    * options are more consistent
+    * deprecated redundant options
+  * run 'bundle exec autotest' when Gemfile is present
+  * support ERB in .rspec options files (Justin Ko)
+  * depend on bundler for development tasks (Myron Marston)
+  * add example_group_finished to formatters and reporter (Roman Chernyatchik)
+
+* Bug fixes
+  * support paths with spaces when using autotest (Andreas Neuhaus)
+  * fix module_exec with ruby 1.8.6 (Myron Marston)
+  * remove context method from top-level
+    * was conflicting with irb, for example
+  * errors in before(:all) are now reported correctly (Chad Humphries)
+
+* Removals
+  * removed -o --options-file command line option
+    * use ./.rspec and ~/.rspec

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/License.txt

@@ -0,0 +1,22 @@
+(The MIT License)
+
+Copyright (c) 2009 David Chelimsky, Chad Humphries
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/README.markdown

@@ -0,0 +1,95 @@
+# RSpec Core
+
+Behaviour Driven Development for Ruby
+
+## Documentation
+
+* [Cucumber features](http://relishapp.com/rspec/rspec-core/v/2-0)
+* [RDoc](http://rubydoc.info/gems/rspec-core/2.0.1/frames)
+
+## Install
+
+    gem install rspec      # for rspec-core, rspec-expectations, rspec-mocks
+    gem install rspec-core # for rspec-core only
+
+## Upgrading from rspec-1.x
+
+See [Upgrade.markdown](http://github.com/rspec/rspec-core/blob/master/Upgrade.markdown)
+
+
+This will install the rspec, rspec-core, rspec-expectations and rspec-mocks
+gems.
+
+## Get Started
+
+Start with a simple example of behavior you expect from your system. Do
+this before you write any implementation code:
+
+    # in spec/calculator_spec.rb
+    describe Calculator, "add" do
+      it "returns the sum of its arguments" do
+        Calculator.new.add(1, 2).should eq(3)
+      end
+    end
+
+Run this with the rspec command, and watch it fail:
+
+    $ rspec spec/calculator_spec.rb
+    ./spec/calculator_spec.rb:1: uninitialized constant Calculator
+
+Implement the simplest solution:
+
+    # in lib/calculator.rb
+    class Calculator
+      def add(a,b)
+        a + b
+      end
+    end
+
+Be sure to require the implementation file in the spec:
+
+    # in spec/calculator_spec.rb
+    # - RSpec adds ./lib to the $LOAD_PATH, so you can
+    #   just require "calculator" directly
+    require "calculator"
+
+Now run the spec again, and watch it pass:
+    
+    $ rspec spec/calculator_spec.rb
+    .
+
+    Finished in 0.000315 seconds
+    1 example, 0 failures
+
+Use the documentation formatter to see the resulting spec:
+
+    $ rspec spec/calculator_spec.rb --format doc
+    Calculator add
+      returns the sum of its arguments
+
+    Finished in 0.000379 seconds
+    1 example, 0 failures
+
+## Known issues
+
+See [http://github.com/rspec/rspec-core/issues](http://github.com/rspec/rspec-core/issues)
+
+## Learn more
+
+While not comprehensive yet, you can learn quite a lot from the Cucumber
+features in the [features
+directory](http://github.com/rspec/rspec-core/tree/master/features/).  If there
+is a feature that is not documented there, or you find them insufficient to
+understand how to use a feature, please submit issues to
+[http://github.com/rspec/rspec-core/issues](http://github.com/rspec/rspec-core/issues).
+
+## Contribute
+
+See [http://github.com/rspec/rspec-dev](http://github.com/rspec/rspec-dev)
+
+## Also see
+
+* [http://github.com/rspec/rspec](http://github.com/rspec/rspec)
+* [http://github.com/rspec/rspec-expectations](http://github.com/rspec/rspec-expectations)
+* [http://github.com/rspec/rspec-mocks](http://github.com/rspec/rspec-mocks)
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/Rakefile

@@ -0,0 +1,71 @@
+require "bundler"
+Bundler.setup
+Bundler::GemHelper.install_tasks
+
+require "rake"
+require "yaml"
+
+require "rake/rdoctask"
+require "rspec/core/rake_task"
+require "rspec/core/version"
+require "cucumber/rake/task"
+
+class Cucumber::Rake::Task::ForkedCucumberRunner
+  # When cucumber shells out, we still need it to run in the context of our
+  # bundle.
+  def run
+    sh "bundle exec #{RUBY} " + args.join(" ")
+  end
+end
+
+desc "Run all examples"
+RSpec::Core::RakeTask.new(:spec) do |t|
+  t.rspec_path = 'bin/rspec'
+  t.rspec_opts = %w[--color]
+end
+
+Cucumber::Rake::Task.new(:cucumber)
+
+namespace :rcov do
+  task :cleanup do
+    rm_rf 'coverage.data'
+  end
+
+  RSpec::Core::RakeTask.new :spec do |t|
+    t.rcov = true
+    t.rcov_opts =  %[-Ilib -Ispec --exclude "gems/*,features"]
+    t.rcov_opts << %[--no-html --aggregate coverage.data]
+  end
+
+  Cucumber::Rake::Task.new :cucumber do |t|
+    t.cucumber_opts = %w{--format progress}
+    t.rcov = true
+    t.rcov_opts =  %[-Ilib -Ispec --exclude "gems/*,features"]
+    t.rcov_opts << %[--text-report --sort coverage --aggregate coverage.data]
+  end
+
+end
+
+task :rcov => ["rcov:cleanup", "rcov:spec", "rcov:cucumber"]
+
+task :default => [:spec, :cucumber]
+
+task :clobber do
+  rm_rf 'pkg'
+  rm_rf 'tmp'
+  rm_rf 'coverage'
+end
+
+desc "Push cukes to relishapp using the relish-client-gem"
+task :relish, :version do |t, args|
+  raise "rake relish[VERSION]" unless args[:version]
+  sh "relish push --organization rspec --project rspec-core -v #{args[:version]}"
+end
+
+Rake::RDocTask.new do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = "rspec-core #{RSpec::Core::Version::STRING}"
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/Upgrade.markdown

@@ -0,0 +1,289 @@
+# New features in rspec-core-2.1
+
+## Command line
+
+### `--tags`
+
+Now you can tag groups and examples using metadata and access those tags from
+the command line. So if you have a group with `:foo => true`:
+
+    describe "something", :foo => true do
+      it "does something" do
+        # ...
+      end
+    end
+
+... now you can run just that group like this:
+
+    rspec spec --tags foo
+
+### `--fail-fast`
+
+Add this flag to the command line to tell rspec to clean up and exit after the
+first failure:
+
+    rspec spec --fail-fast
+
+## Metata/filtering
+
+### :if and :unless keys
+
+Use :if and :unless keys to conditionally run examples with simple boolean
+expressions:
+
+    describe "something" do
+      it "does something", :if => RUBY_VERSION == 1.8.6 do
+        # ...
+      end
+      it "does something", :unless => RUBY_VERSION == 1.8.6 do
+        # ...
+      end
+    end
+
+## Conditionally 'pending' examples
+
+Make examples pending based on a condition.  This is most useful when you
+have an example that runs in multiple contexts and fails in one of those due to
+a bug in a third-party dependency that you expect to be fixed in the future.
+
+    describe "something" do
+      it "does something that doesn't yet work right on JRuby" do
+        pending("waiting for the JRuby team to fix issue XYZ", :if => RUBY_PLATFORM == 'java') do
+          # the content of your spec
+        end
+      end
+    end
+
+This example would run normally on all ruby interpretters except JRuby.  On JRuby,
+it uses the block form of `pending`, which causes the example to still be run and
+will remain pending as long as it fails.  In the future, if you upgraded your
+JRuby installation to a newer release that allows the example to pass, RSpec
+will report it as a failure (`Expected pending '...' to fail.  No Error was raised.`),
+so that know that you can remove the call to `pending`.
+
+# New features in rspec-core-2.0
+
+### Runner
+
+The new runner for rspec-2 comes from Micronaut.
+
+### Metadata!
+
+In rspec-2, every example and example group comes with metadata information
+like the file and line number on which it was declared, the arguments passed to
+`describe` and `it`, etc.  This metadata can be appended to through a hash
+argument passed to `describe` or `it`, allowing us to pre and post-process
+each example in a variety of ways.
+
+### Filtering
+
+The most obvious use is for filtering the run. For example:
+
+    # in spec/spec_helper.rb
+    RSpec.configure do |c|
+      c.filter_run :focus => true
+    end
+
+    # in any spec file
+    describe "something" do
+      it "does something", :focus => true do
+        # ....
+      end
+    end
+
+When you run the `rspec` command, rspec will run only the examples that have
+`:focus => true` in the hash. 
+
+You can also add `run_all_when_everything_filtered` to the config:
+
+    RSpec.configure do |c|
+      c.filter_run :focus => true
+      c.run_all_when_everything_filtered = true
+    end
+
+Now if there are no examples tagged with `:focus => true`, all examples
+will be run. This makes it really easy to focus on one example for a
+while, but then go back to running all of the examples by removing that
+argument from `it`. Works with `describe` too, in which case it runs
+all of the examples in that group.
+
+The configuration will accept a lambda, which provides a lot of flexibility
+in filtering examples. Say, for example, you have a spec for functionality that
+behaves slightly differently in Ruby 1.8 and Ruby 1.9. We have that in
+rspec-core, and here's how we're getting the right stuff to run under the
+right version:
+
+    # in spec/spec_helper.rb
+    RSpec.configure do |c|
+      c.exclusion_filter = { :ruby => lambda {|version|
+        !(RUBY_VERSION.to_s =~ /^#{version.to_s}/)
+      }}
+    end
+
+    # in any spec file
+    describe "something" do
+      it "does something", :ruby => 1.8 do
+        # ....
+      end
+
+      it "does something", :ruby => 1.9 do
+        # ....
+      end
+    end
+
+In this case, we're using `exclusion_filter` instead of `filter_run` or
+`filter`, which indicate _inclusion_ filters. So each of those examples is
+excluded if we're _not_ running the version of Ruby they work with.
+
+### Shared example groups
+
+Shared example groups are now run in a nested group within the including group
+(they used to be run in the same group). Nested groups inherit `before`, `after`,
+`around`, and `let` hooks, as well as any methods that are defined in the parent
+group.
+
+This new approach provides better encapsulation, better output, and an
+opportunity to add contextual information to the shared group via a block
+passed to `it_should_behave_like`.
+
+See [features/example\_groups/shared\_example\_group.feature](http://github.com/rspec/rspec-core/blob/master/features/example_groups/shared_example_group.feature) for more information.
+
+NOTICE: The including example groups no longer have access to any of the
+methods, hooks, or state defined inside a shared group. This will break specs
+that were using shared example groups to extend the behavior of including
+groups in any way besides their intended purpose: to add examples to a group.
+
+# Upgrading from rspec-1.x
+
+### rspec command
+
+The command to run specs is now `rspec` instead of `spec`.
+
+    rspec ./spec
+
+#### Co-habitation of rspec-1 and rspec-2
+
+Early beta versions of RSpec-2 included a `spec` command, which conflicted with
+the RSpec-1 `spec` command because RSpec-1's was installed by the rspec gem,
+while RSpec-2's is installed by the rspec-core gem.
+
+If you installed one of these early versions, the safest bet is to uninstall
+rspec-1 and rspec-core-2, and then reinstall both. After you do this, you will
+be able to run rspec-2 like this:
+
+    rspec ./spec
+
+... and rspec-1 like this:
+
+    spec _1.3.1_ ./spec
+
+Rubygems inspects the first argument to any gem executable to see if it's
+formatted like a version number surrounded by underscores. If so, it uses that
+version (e.g.  `1.3.1`). If not, it uses the most recent version (e.g.
+`2.0.0`).
+
+### rake task
+
+A few things changed in the Rake task used to run specs:
+
+1.  The file in which it is defined changed from `spec/rake/spectask` to
+    `rspec/core/rake_task`
+
+2.  The `spec_opts` accessor has been deprecated in favor of `rspec_opts`. Also,
+    the `rspec` command no longer supports the `--options` command line option
+    so the options must be embedded directly in the Rakefile, or stored in the
+    `.rspec` files mentioned above.
+    
+3.  In RSpec-1, the rake task would read in rcov options from an `rcov.opts`
+    file. This is ignored by RSpec-2. RCov options are now set directly on the Rake
+    task:
+
+        RSpec::Core::RakeTask.new(:rcov) do |t|
+          t.rcov_opts =  %q[--exclude "spec"]
+        end
+
+3.  The `spec_files` accessor has been replaced by `pattern`.
+
+        # rspec-1
+        require 'spec/rake/spectask'
+
+        Spec::Rake::SpecTask.new do |t|
+          t.spec_opts = ['--options', "\"spec/spec.opts\""]
+          t.spec_files = FileList['spec/**/*.rb']
+        end
+
+        # rspec-2
+        require 'rspec/core/rake_task'
+
+        RSpec::Core::RakeTask.new do |t|
+          t.rspec_opts = ["-c", "-f progress", "-r ./spec/spec_helper.rb"]
+          t.pattern = 'spec/**/*_spec.rb'
+        end
+
+### autotest
+
+RSpec-2 works with autotest as follows:
+
+    rspec --configure autotest
+
+This adds `./autotest/discover.rb` with:
+
+    Autotest.add_discovery { "rspec2" }
+
+Now, on the command line just type:
+
+    autotest
+
+Or, if you're using bundler:
+
+    bundle exec autotest
+
+The `autospec` command is a thing of the past. 
+
+### RSpec is the new Spec
+
+The root namespace (top level module) is now `RSpec` instead of `Spec`, and
+the root directory under `lib` within all of the `rspec` gems is `rspec` instead of `spec`.
+
+### Configuration
+
+Typically in `spec/spec_helper.rb`, configuration is now done like this:
+
+    RSpec.configure do |c|
+      # ....
+    end
+
+### .rspec
+
+Command line options can be persisted in a `.rspec` file in a project. You
+can also store a `.rspec` file in your home directory (`~/.rspec`) with global
+options. Precedence is:
+
+    command line
+    ./.rspec
+    ~/.rspec
+
+### `context` is no longer a top-level method
+
+We removed `context` from the main object because it was creating conflicts with
+IRB and some users who had `Context` domain objects. `describe` is still there,
+so if you want to use `context` at the top level, just alias it:
+
+    alias :context :describe
+
+Of course, you can still use `context` to declare a nested group:
+
+    describe "something" do
+      context "in some context" do
+        it "does something" do
+          # ...
+        end
+      end
+    end
+
+### `$KCODE` no longer set implicitly to `'u'`
+
+In RSpec-1, the runner set `$KCODE` to `'u'`, which impacts, among other
+things, the behaviour of Regular Expressions when applied to non-ascii
+characters. This is no longer the case in RSpec-2.
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/autotest/discover.rb

@@ -0,0 +1,2 @@
+Autotest.add_discovery { "rspec2" }
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/bin/autospec

@@ -0,0 +1,13 @@
+#!/usr/bin/env ruby
+require 'rspec/core/deprecation'
+RSpec.warn_deprecation <<-WARNING
+************************************************************
+REMOVAL NOTICE: you are using behaviour that has been
+removed from rspec-2.
+
+* The 'autospec' command is no longer supported.
+* Please use 'autotest' insted.
+
+This message will be removed from a future version of rspec.
+************************************************************
+WARNING

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/bin/rspec

@@ -0,0 +1,25 @@
+#!/usr/bin/env ruby
+
+begin
+  require 'rspec/autorun'
+rescue LoadError
+  $stderr.puts <<-EOS
+#{'*'*50}
+  Could not find 'rspec/autorun'
+
+  This may happen if you're using rubygems as your package manager, but it is not
+  being required through some mechanism before executing the rspec command.
+
+  You may need to do one of the following in your shell:
+
+    # for bash/zsh
+    export RUBYOPT=rubygems
+
+    # for csh, etc.
+    set RUBYOPT=rubygems
+
+  For background, please see http://gist.github.com/54177.
+#{'*'*50}
+  EOS
+  exit(1)
+end

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/cucumber.yml

@@ -0,0 +1,2 @@
+default: --require features --strict --format progress --tags ~@wip features
+wip:     --require features --tags @wip:3 --wip features

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/README.markdown

@@ -0,0 +1,19 @@
+rspec-core provides the structure for RSpec code examples:
+
+    describe Account do
+      it "has a balance of zero when first opened" do
+        # example code goes here - for more on the 
+        # code inside the examples, see rspec-expectations 
+        # and rspec-mocks
+      end
+    end
+
+## Issues
+
+The documentation for rspec-core is a work in progress. We'll be adding
+Cucumber features over time, and clarifying existing ones.  If you have
+specific features you'd like to see added, find the existing documentation
+incomplete or confusing, or, better yet, wish to write a missing Cucumber
+feature yourself, please [submit an
+issue](http://github.com/rspec/rspec-core/issues) or a [pull
+request](http://github.com/rspec/rspec-core).

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/configure.feature

@@ -0,0 +1,20 @@
+Feature: configure
+
+  Use the --configure option on the command line to generate configuration
+  files.
+
+  The only supported argument, so far, is "autotest", which creates an
+  autotest/discover.rb file in your project root directory.
+
+  Background:
+    Given a directory named "rspec_project"
+
+  Scenario: generate autotest directory and discover file
+    When I cd to "rspec_project"
+    And I run "rspec --configure autotest"
+    Then the following directories should exist:
+      | autotest |
+    And the following files should exist:
+      | autotest/discover.rb |
+    And the file "autotest/discover.rb" should contain "Autotest.add_discovery"
+    And the stdout should contain "autotest/discover.rb has been added"