shoe 0.6.1 → 0.6.2

data/.gitignore

@@ -1,4 +0,0 @@
-.bundle
-.rvmrc
-*.gem
-rdoc

data/BUNDLER.rdoc

@@ -1,16 +0,0 @@
-= Using Shoe with {Bundler}[http://gembundler.com]
-
-Bootstrapping is a little chicken-and-egg-y, but with the following initial <tt>Gemfile</tt>:
-
- source :rubygems
- gem 'shoe', :group => :development
-
-You should be able to:
-
- $ bundle install
- $ bundle exec shoe .
-
-From there, I've been preferring <tt>`bundle exec bash`</tt> over <tt>`bundle
-exec rake`</tt> or using <tt>require 'bundler/setup'</tt> in my
-<tt>Rakefile</tt>. But, if you're using Bundler, you're probably already used
-to puzzling over such things!

data/Gemfile

@@ -1,9 +0,0 @@
-source :rubygems
-
-gem 'rake'
-gem 'launchy'
-
-group :development do
-  gem 'cucumber'
-  gem 'ronn'
-end

data/Gemfile.lock

@@ -1,49 +0,0 @@
---- 
-dependencies: 
-  ronn: 
-    group: 
-    - :development
-    version: ">= 0"
-  rake: 
-    group: 
-    - :default
-    version: ">= 0"
-  cucumber: 
-    group: 
-    - :development
-    version: ">= 0"
-  launchy: 
-    group: 
-    - :default
-    version: ">= 0"
-specs: 
-- rake: 
-    version: 0.8.7
-- builder: 
-    version: 2.1.2
-- configuration: 
-    version: 1.1.0
-- diff-lcs: 
-    version: 1.1.2
-- json_pure: 
-    version: 1.2.4
-- polyglot: 
-    version: 0.3.1
-- term-ansicolor: 
-    version: 1.0.5
-- treetop: 
-    version: 1.4.5
-- cucumber: 
-    version: 0.6.4
-- hpricot: 
-    version: 0.8.2
-- launchy: 
-    version: 0.3.5
-- rdiscount: 
-    version: 1.6.3
-- ronn: 
-    version: "0.5"
-hash: d47953731e3f472755d844fb72d2644ea08f56d9
-sources: 
-- Rubygems: 
-    uri: http://gemcutter.org

data/Rakefile

@@ -1,4 +0,0 @@
-$:.unshift 'lib'
-require 'shoe'
-
-Shoe::Tasks.define('shoe.gemspec')

data/cucumber.yml

@@ -1,2 +0,0 @@
-default: --format progress --tags ~@wip
-wip: --tags @wip --wip

data/features/cucumber.feature

@@ -1,27 +0,0 @@
-Feature: Cucumber
-  In order to use cucumber conveniently
-  As a developer
-  I want shoe to give me a rake task
-
-  Scenario: Running rake --tasks in a shoe project without Cucumber features
-    Given I have run shoe my_project inside "."
-    When I run rake --tasks inside "my_project"
-    Then I should not see "rake cucumber" on standard out
-
-  Scenario: Running rake --tasks in a shoe project with Cucumber features
-    Given I have run shoe my_project inside "."
-    And I have run git init inside "."
-    And I have created a file called "my_project/cucumber.yml" containing:
-      """
-      default: --tags ~@wip
-      wip: --tags @wip --wip
-      """
-    When I run rake --tasks inside "my_project"
-    Then I should see "rake cucumber" on standard out
-    And I should see "rake cucumber:wip" on standard out
-
-  Scenario: Running rake --tasks in a shoe project with a bad cucumber.yml
-    Given I have run shoe my_project inside "."
-    And I have created a file called "my_project/cucumber.yml" containing ""
-    When I run rake --tasks inside "my_project"
-    Then I should not see "rake cucumber" on standard out

data/features/generator.feature

@@ -1,32 +0,0 @@
-Feature: Getting started
-  In order to start using shoe
-  As a developer
-  I want a little help generating my Rakefile
-
-  Scenario: Running shoe to create a new project
-    When I run shoe my_project inside "."
-    Then I should see a file "my_project/.gitignore"
-    And I should see a file "my_project/Rakefile"
-    And I should see a file "my_project/README.rdoc"
-    And I should see a file "my_project/lib/my_project.rb"
-    And I should see a file "my_project/test/helper.rb"
-    And I should see a file "my_project/test/my_project_test.rb"
-    And I should see a file "my_project/my_project.gemspec"
-
-  Scenario: Running shoe --application to create a new project
-    When I run shoe --application my_project inside "."
-    Then I should see a file "my_project/bin/my_project"
-    And I should see a file "my_project/lib/my_project/application.rb"
-
-  Scenario: Running shoe --extension to create a new project
-    When I run shoe --extension my_project inside "."
-    Then I should see a file "my_project/ext/my_project/extconf.rb"
-    And I should see a file "my_project/ext/my_project/extension.c"
-
-  Scenario: Running shoe with no arguments in an existing project that already has a Rakefile
-    Given I have created a directory called "my_project"
-    And I have created a file called "my_project/Rakefile" containing "# RAKEFILE CONTENTS"
-    When I run shoe inside "my_project"
-    Then I should see "WARN: not clobbering existing Rakefile" on standard error
-    And the contents of "my_project/Rakefile" should still be "# RAKEFILE CONTENTS"
-

data/features/release.feature

@@ -1,33 +0,0 @@
-Feature: Release
-  In order to conveniently make a release of my project
-  As a developer
-  I want shoe to give me a rake task
-
-  Background:
-    Given I have created a directory called "origin"
-    And I have run git init --bare inside "origin"
-    Given I have run shoe my_project inside "."
-    And I have run git init inside "my_project"
-    And I have run git add . inside "my_project"
-    And I have run git commit -m "Initial commit" inside "my_project"
-
-  Scenario: I can release
-    When I replace "0.0.0" with "0.1.0" in the file "my_project/lib/my_project.rb"
-    And I run rake --tasks inside "my_project"
-    Then I should see "rake release" on standard out
-
-  Scenario: I cannot release when the version is 0.0.0
-    When I run rake --tasks inside "my_project"
-    Then I should not see "rake release" on standard out
-
-  Scenario: I cannot release when I already have a tag for the current version
-    When I run git tag v0.1.0 inside "my_project"
-    And I replace "0.0.0" with "0.1.0" in the file "my_project/lib/my_project.rb"
-    And I run rake --tasks inside "my_project"
-    Then I should not see "rake release" on standard out
-
-  Scenario: I cannot release from a branch other than master
-    When I run git checkout -b topic inside "my_project"
-    And I replace "0.0.0" with "0.1.0" in the file "my_project/lib/my_project.rb"
-    And I run rake --tasks inside "my_project"
-    Then I should not see "rake release" on standard out

data/features/step_definitions/shoe_steps.rb

@@ -1,39 +0,0 @@
-Given /^I have created a directory called "([^\"]*)"$/ do |name|
-  create_directory(name)
-end
-
-Given /^I have created a file called "([^\"]*)" containing "([^\"]*)"$/ do |path, contents|
-  create_file(path, contents)
-end
-
-Given /^I have created a file called "([^\"]*)" containing:$/ do |path, contents|
-  create_file(path, contents)
-end
-
-Given /^I have appended "([^\"]*)" to "([^\"]*)"$/ do |contents, path|
-  append_file(path, contents)
-end
-
-When /^I replace "([^\"]*)" with "([^\"]*)" in the file "([^\"]*)"$/ do |search, replace, path|
-  edit_file(path, search, replace)
-end
-
-When /^I (?:have )?run (.*) inside "([^\"]*)"$/ do |command, path|
-  run(command, path)
-end
-
-Then /^I should(.*) see "([^\"]*)" on (standard.*)$/ do |negate, message, standard_out_or_error|
-  standard_out_or_error.tr!(' ', '_')
-  am_i_expecting_to_see_something = negate.strip.empty?
-  contents = send(standard_out_or_error)
-
-  assert_equal am_i_expecting_to_see_something, contents.include?(message), contents
-end
-
-Then /^I should see a file "([^\"]*)"$/ do |path|
-  assert file(path).exist?
-end
-
-Then /^the contents of "([^\"]*)" should still be "([^\"]*)"$/ do |path, expected|
-  assert_equal expected, file(path).read
-end

data/features/support/env.rb

@@ -1,69 +0,0 @@
-require 'open3'
-require 'pathname'
-require 'test/unit/assertions'
-require 'tmpdir'
-
-class WorkingDirectory
-  PROJECT_ROOT = Pathname.new(File.expand_path('../../..', __FILE__))
-
-  attr_reader :working_directory
-  attr_reader :standard_out
-  attr_reader :standard_error
-
-  def initialize
-    @working_directory = Pathname.new(Dir.mktmpdir)
-  end
-
-  def create_directory(path)
-    file(path).mkpath
-  end
-
-  def create_file(path, contents)
-    file(path).open('w') { |file| file.write(contents) }
-  end
-
-  def append_file(path, contents)
-    file(path).open('a') { |file| file.write(contents) }
-  end
-
-  def edit_file(path, search, replace)
-    old_contents = file(path).read
-    new_contents = old_contents.gsub(search, replace)
-    create_file(path, new_contents)
-  end
-
-  def file(path)
-    working_directory.join(path)
-  end
-
-  def run(command, path)
-    Dir.chdir(working_directory.join(path)) do
-      Open3.popen3(isolate_environment(command)) do |stdin, stdout, stderr|
-        @standard_out   = stdout.read
-        @standard_error = stderr.read
-      end
-    end
-  end
-
-  private
-
-  def isolate_environment(command)
-    # set the PATH so tests can just run shoe
-    ENV['PATH'] = ENV['PATH'].split(File::PATH_SEPARATOR).
-                            unshift(PROJECT_ROOT.join('bin')).uniq.
-                               join(File::PATH_SEPARATOR)
-    ENV['RUBYLIB'] = PROJECT_ROOT.join('lib')
-
-    # whack most environment variables for good hygiene
-    "/usr/bin/env -i #{preserve_environment 'HOME', 'PATH', 'GEM_HOME', 'GEM_PATH', 'RUBYLIB'} #{command}"
-  end
-
-  def preserve_environment(*variables)
-    variables.map { |name| "#{name}='#{ENV[name]}'" }.join(' ')
-  end
-end
-
-World(Test::Unit::Assertions)
-World  { WorkingDirectory.new }
-Before { working_directory.mkpath }
-After  { working_directory.rmtree }

data/features/test.feature

@@ -1,18 +0,0 @@
-Feature: Test
-  In order to run tests
-  As a developer
-  I want shoe to give me a rake task
-
-  Scenario: Running rake --tasks in a shoe project without tests
-    Given I have run shoe --no-test-unit my_project inside "."
-    And I have run git init inside "my_project"
-    When I run rake --tasks inside "my_project"
-    Then I should not see "rake test" on standard out
-
-  Scenario: Running rake --tasks in a shoe project with tests
-    Given I have run shoe --no-test-unit my_project inside "."
-    And I have run git init inside "my_project"
-    And I have created a directory called "my_project/test"
-    And I have created a file called "my_project/test/foo_test.rb" containing ""
-    When I run rake --tasks inside "my_project"
-    Then I should see "rake test" on standard out

data/shoe.gemspec

@@ -1,44 +0,0 @@
-$:.unshift File.expand_path('../lib', __FILE__)
-require 'shoe'
-
-Gem::Specification.new do |spec|
-  spec.name    = 'shoe'
-  spec.version = Shoe::VERSION
-
-  spec.summary = 'An ecosystem-friendly library of Rake tasks for your gem.'
-  spec.description = <<-END.gsub(/^ */, '')
-    #{spec.summary}
-
-    Shoe assumes you could be using any number of other tools -- bundler,
-    cucumber, git, rip, rubygems -- and so leans hard on them for the things
-    they do well, relegating command-line rake to mere syntactic sugar.
-  END
-
-  spec.author = 'Matthew Todd'
-  spec.email  = 'matthew.todd@gmail.com'
-  spec.homepage = 'http://github.com/matthewtodd/shoe'
-
-  spec.requirements = ['git']
-  spec.required_rubygems_version = '>= 1.3.6'
-  spec.add_runtime_dependency 'rake'
-  spec.add_runtime_dependency 'launchy'
-  spec.add_development_dependency 'cucumber'
-  spec.add_development_dependency 'ronn'
-
-  def spec.git_files(glob=nil)
-    `git ls-files -z --cached --other --exclude-standard #{glob}`.split("\0")
-  end
-
-  spec.files       = spec.git_files
-  spec.executables = spec.git_files('bin/*').map &File.method(:basename)
-  spec.extensions  = spec.git_files('ext/**/extconf.rb')
-  spec.test_files  = spec.git_files('test/{,**/}*_test.rb')
-
-  spec.extra_rdoc_files = spec.git_files('{,**/}*.rdoc')
-  spec.rdoc_options     = %W(
-    --main README.rdoc
-    --title #{spec.full_name}
-    --inline-source
-    --webcvs http://github.com/matthewtodd/shoe/blob/v#{spec.version}/
-  )
-end