jeweler 1.4.0 → 1.5.0.pre2

data/.document

@@ -0,0 +1,14 @@
+# .document is used by rdoc and yard to know how to generate documentation 
+# for example, it can be used to control how rdoc gets built when you do `gem install foo`
+
+lib/jeweler.rb
+lib/jeweler/*.rb
+lib/jeweler/commands/*.rb
+lib/jeweler/generator/*.rb
+bin/*
+
+# Files below the line with - are treated as 'extra files', and aren't parsed for ruby code
+-
+README.markdown
+features/**/*.feature
+LICENSE

data/.gitignore

@@ -1,10 +1,21 @@
+# bundler
+.bundle
+
+# rcov generated
 coverage
+
+# jeweler generated
 pkg
+
+# yard generated
 doc
-rdoc
+.yardoc
+
+# ctags generated
 tags
+
+# tmp directories used during testing
 test/tmp
 test/jeweler/version_tmp
 test/version_tmp
 tmp
-.yardoc

data/ChangeLog.markdown

@@ -8,12 +8,12 @@
  * `rake install` should correctly figure out which `gem` binary to invoke now
  * `rake build` now will regenerate the gemspec as well
  * `rake gemspec` now eliminates duplicates for gemspec.files, gemspec.rdoc_files, etc
- * `rake gemspec` now automtically populate gemspec.extensions with any extconf.rb files you have in `ext`
+ * `rake gemspec` now automatically populates gemspec.extensions with any extconf.rb files you have in `ext`
  * Releasing to Rubyforge is now deprecated in favor of Gemcutter.
 
 # jeweler 1.3.0
 
- * Now supports an addition version type, build. This can be used to add a fourth segment of the version that's arbirtary. One example use is having prereleases.
+ * Now supports an additional version type, build. This can be used to add a fourth segment of the version that's arbitrary. One example use is having prereleases.
  * Jeweler now lazily loads, to avoid causing side-effects when running other rake tasks
  * Version can now be set explicitly on the gemspec, rather than relying on a VERSION file
  * Rubyforge and Gemcutter support now hooks into `rake release`
@@ -21,7 +21,7 @@
  * Rubyforge support no longer forces the uploading of documentation
  * Generator:
   * Allow arbitrary homepage and git remotes, to decouple a bit from GitHub
-  * Support for the riot testing framework: http://github.com/thumblemonks/riot/ 
+  * Support for the riot testing framework: http://github.com/thumblemonks/riot/
   * Support for test/spec
   * .gitignore now ignores emacs temporary files
   * rspec support now creates a spec.opts with support for color and other stuff
@@ -76,7 +76,7 @@
  * Managing a gemspec's files, test_files, and extra_rdoc_files is now more flexible. They are now wrapped in a FileList, so you can easily 'include' or 'exclude' patterns.
 
 # jeweler 0.10.2 2009-03-26
- 
+
  * 'rake install' now will 'rake build' first
  * Support for releasing to RubyForge, thanks to jtrupiano
  * Steps towards Ruby 1.9 support, thanks to rsanheim
@@ -85,19 +85,19 @@
 
  * Tasks:
   * Fixed populating default spec's extra_rdoc_files
-  * Removed redudant gem building/installing tasks. Use rake build and rake install
+  * Removed redundant gem building/installing tasks. Use rake build and rake install
  * Generator:
   * Added support for micronaut
   * Generate nicer block variable names in Rakefile
   * Cucumber generation now places steps in features/step_features, to follow cucumber standards
 
-  * shoulda and test/unit test_helpers no longers require mocha 
+  * shoulda and test/unit test_helpers no longer require mocha
   * Rakefile uses more readable block variable names
   * .gitignore now includes pkg and coverage directories
   * Avoid puts'ing in Rakefile when LoadError occurs. Instead, define a task that aborts with instructions to install.
   * Cucumber is now optional. Generate stories using --cucumber
   * Bacon's 'test' task is now 'spec'
-  * Generate README.rdoc instead of just a plain text README 
+  * Generate README.rdoc instead of just a plain text README
   * Updated year in README.rdoc and COPYRIGHT to be based on the current year instead of hardcoded
 
 # jeweler 0.8.1 2009-02-03
@@ -114,7 +114,7 @@
   * Added support for cucumber
   * Creating a new gem is now more verbose, and will show files/directories created
  * Binaries will now be automatically detected in 'bin'
-  
+
 # jeweler 0.7.2 2009-01-29
 
  * Added rake task 'version:bump' which is shorthand for 'version:bump:patch'

data/Gemfile

@@ -0,0 +1,21 @@
+source 'http://gemcutter.org'
+source 'http://gems.github.com'
+
+gem "rake"
+gem "git", ">= 1.2.5"
+gem "bundler", ">= 1.0.0.rc.5"
+
+group :development do
+  gem "shoulda"
+  gem "mhennemeyer-output_catcher"
+  gem "rr"
+  gem "mocha"
+  gem "redgreen"
+  gem "test-construct"
+  gem "yard"
+  gem "cucumber"
+  gem "rcov"
+  gem "timecop"
+  gem "activesupport", "~> 2.3.5"
+  gem "ruby-debug"
+end

data/Gemfile.lock

@@ -0,0 +1,57 @@
+GEM
+  remote: http://gemcutter.org/
+  remote: http://gems.github.com/
+  specs:
+    activesupport (2.3.8)
+    builder (2.1.2)
+    columnize (0.3.1)
+    cucumber (0.8.5)
+      builder (~> 2.1.2)
+      diff-lcs (~> 1.1.2)
+      gherkin (~> 2.1.4)
+      json_pure (~> 1.4.3)
+      term-ansicolor (~> 1.0.4)
+    diff-lcs (1.1.2)
+    gherkin (2.1.5)
+      trollop (~> 1.16.2)
+    git (1.2.5)
+    json_pure (1.4.6)
+    linecache (0.43)
+    mhennemeyer-output_catcher (1.0.1)
+    mocha (0.9.8)
+      rake
+    rake (0.8.7)
+    rcov (0.9.8)
+    redgreen (1.2.2)
+    rr (0.10.11)
+    ruby-debug (0.10.3)
+      columnize (>= 0.1)
+      ruby-debug-base (~> 0.10.3.0)
+    ruby-debug-base (0.10.3)
+      linecache (>= 0.3)
+    shoulda (2.11.3)
+    term-ansicolor (1.0.5)
+    test-construct (1.2.0)
+    timecop (0.3.5)
+    trollop (1.16.2)
+    yard (0.5.8)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activesupport (~> 2.3.5)
+  bundler (>= 1.0.0.rc.5)
+  cucumber
+  git (>= 1.2.5)
+  mhennemeyer-output_catcher
+  mocha
+  rake
+  rcov
+  redgreen
+  rr
+  ruby-debug
+  shoulda
+  test-construct
+  timecop
+  yard

data/README.markdown

@@ -14,8 +14,8 @@ Jeweler provides two things:
 
 ## Installing
 
-    # Install the gem:
-    sudo gem install jeweler
+# Install the gem:
+    gem install jeweler
 
 ## Using in an existing project
 
@@ -32,7 +32,7 @@ It's easy to get up and running. Update your Rakefile to instantiate a `Jeweler:
         gemspec.authors = ["Josh Nichols"]
       end
     rescue LoadError
-      puts "Jeweler not available. Install it with: sudo gem install jeweler"
+      puts "Jeweler not available. Install it with: gem install jeweler"
     end
 
 The yield object here, `gemspec`, is a `Gem::Specification` object. See the [Customizing your project's gem specification](http://wiki.github.com/technicalpickles/jeweler/customizing-your-projects-gem-specification) for more details about how you can customize your gemspec.
@@ -151,7 +151,7 @@ A Rakefile setup for gemcutter would include something like this:
       end
       Jeweler::GemcutterTasks.new
     rescue LoadError
-      puts "Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler"
+      puts "Jeweler (or a dependency) not available. Install it with: gem install jeweler"
     end
 
 
@@ -167,7 +167,7 @@ Jeweler can also handle releasing to [RubyForge](http://rubyforge.org). There ar
 
  * [Create an account on RubyForge](http://rubyforge.org/account/register.php)
  * Request a project on RubyForge.
- * Install the RubyForge gem: sudo gem install rubyforge
+ * Install the RubyForge gem: gem install rubyforge
  * Run 'rubyforge setup' and fill in your username and password for RubyForge
  * Run 'rubyforge config' to pull down information about your projects
  * Run 'rubyforge login' to make sure you are able to login
@@ -188,7 +188,7 @@ A Rakefile setup for rubyforge would include something like this:
         rubyforge.doc_task = "rdoc"
       end
     rescue LoadError
-      puts "Jeweler, or a dependency, not available. Install it with: sudo gem install jeweler"
+      puts "Jeweler, or a dependency, not available. Install it with: gem install jeweler"
     end
 
 Now you must initially create a 'package' for your gem in your RubyForge 'project':

data/Rakefile

@@ -1,32 +1,27 @@
 require 'rake'
+require 'bundler'
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
 
 $LOAD_PATH.unshift('lib')
 
 require 'jeweler'
 Jeweler::Tasks.new do |gem|
   gem.name = "jeweler"
-  gem.summary = "Simple and opinionated helper for creating Rubygem projects on GitHub"
+  gem.version = Jeweler::Version::STRING
+  gem.summary = "Opinionated tool for creating and managing RubyGem projects"
   gem.email = "josh@technicalpickles.com"
   gem.homepage = "http://github.com/technicalpickles/jeweler"
   gem.description = "Simple and opinionated helper for creating Rubygem projects on GitHub"
   gem.authors = ["Josh Nichols"]
   gem.files.include %w(lib/jeweler/templates/.document lib/jeweler/templates/.gitignore)
 
-  gem.add_dependency "git", ">= 1.2.5"
-  gem.add_dependency "rubyforge", ">= 2.0.0"
-  gem.add_dependency "gemcutter", ">= 0.1.0"
-
-  gem.rubyforge_project = "pickles"
-
-  gem.add_development_dependency "thoughtbot-shoulda"
-  gem.add_development_dependency "mhennemeyer-output_catcher"
-  gem.add_development_dependency "rr"
-  gem.add_development_dependency "mocha"
-  gem.add_development_dependency "redgreen"
-  gem.add_development_dependency "devver-construct"
-
-  gem.add_development_dependency "yard"
-  gem.add_development_dependency "cucumber"
+  # dependencies defined in Gemfile
 end
 
 Jeweler::GemcutterTasks.new
@@ -45,41 +40,35 @@ Rake::TestTask.new(:test) do |test|
   test.verbose = true
 end
 
-begin
-  require 'yard'
-  YARD::Rake::YardocTask.new(:yardoc) do |t|
-    t.files   = FileList['lib/**/*.rb'].exclude('lib/jeweler/templates/**/*.rb')
+namespace :test do
+  task :gemspec_dup do
+    gemspec = Rake.application.jeweler.gemspec
+    dupped_gemspec = gemspec.dup
+    cloned_gemspec = gemspec.clone
+    puts gemspec.to_ruby
+    puts dupped_gemspec.to_ruby
   end
-rescue LoadError
-  task :yardoc => :check_dependencies
 end
 
+require 'yard'
+YARD::Rake::YardocTask.new(:yardoc) do |t|
+  t.files   = FileList['lib/**/*.rb'].exclude('lib/jeweler/templates/**/*.rb')
+end
 
-begin
-  require 'rcov/rcovtask'
-  Rcov::RcovTask.new(:rcov => :check_dependencies) do |rcov|
-    rcov.libs << 'test'
-    rcov.pattern = 'test/**/test_*.rb'
-  end
-rescue
-  task :rcov => :check_dependencies
+require 'rcov/rcovtask'
+Rcov::RcovTask.new(:rcov => :check_dependencies) do |rcov|
+  rcov.libs << 'test'
+  rcov.pattern = 'test/**/test_*.rb'
 end
 
-begin
-  require 'cucumber/rake/task'
-  Cucumber::Rake::Task.new(:features) do |features|
+require 'cucumber/rake/task'
+Cucumber::Rake::Task.new(:features) do |features|
+  features.cucumber_opts = "features --format progress"
+end
+namespace :features do
+  Cucumber::Rake::Task.new(:pretty) do |features|
     features.cucumber_opts = "features --format progress"
   end
-  namespace :features do
-    Cucumber::Rake::Task.new(:pretty) do |features|
-      features.cucumber_opts = "features --format progress"
-    end
-  end
-rescue LoadError
-  task :features => :check_dependencies
-  namespace :features do
-    task :pretty => :check_dependencies
-  end
 end
 
 if ENV["RUN_CODE_RUN"] == "true"
@@ -88,6 +77,3 @@ else
   task :default => :test
 end
 
-
-task :test => :check_dependencies
-task :features => :check_dependencies

data/features/generator/cucumber.feature

@@ -25,8 +25,28 @@ Feature: generating cucumber stories
     And a file named 'the-perfect-gem/features/support/env.rb' is created
     And a file named 'the-perfect-gem/features/step_definitions/the-perfect-gem_steps.rb' is created
 
+    And 'features/support/env.rb' requires 'bundler'
+    And 'features/support/env.rb' sets up bundler using the default and development groups
     And 'features/support/env.rb' requires 'the-perfect-gem'
 
+  Scenario: bundler
+    Given a working directory
+    And I want bundler
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'features/support/env.rb' requires 'bundler'
+    And 'features/support/env.rb' sets up bundler using the default and development groups
+
+  Scenario: no bundler
+    Given a working directory
+    And I have configured git sanely
+    And I do not want bundler
+    And I want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'features/support/env.rb' does not require 'bundler'
+    And 'features/support/env.rb' does not setup bundler
+
   Scenario: cucumber setup for bacon
     Given a working directory
     And I have configured git sanely

data/features/generator/directory_layout.feature

@@ -74,3 +74,13 @@ Feature: generated directory layout
 
     And a file named 'the-perfect-gem/examples/example_helper.rb' is created
     And a file named 'the-perfect-gem/examples/the-perfect-gem_example.rb' is created
+
+  Scenario: shindo
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/tests' is created
+
+    And a file named 'the-perfect-gem/tests/tests_helper.rb' is created
+    And a file named 'the-perfect-gem/tests/the-perfect-gem_tests.rb' is created

data/features/generator/gemfile.feature

@@ -0,0 +1,71 @@
+Feature: generated Gemfiel
+  In order to start a new gem
+  A user should be able to
+  generate a Gemfile
+
+  Background:
+    Given a working directory
+    And I have configured git sanely
+
+  Scenario: disabled
+    Given I do not want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gemGemfile' is not created
+
+  Scenario: enabled
+    Given I want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gem/Gemfile' is created
+
+  Scenario: default
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gem/Gemfile' is created
+    And 'Gemfile' uses the gemcutter source
+    And 'Gemfile' has a development dependency on 'bundler'
+    And 'Gemfile' has a development dependency on the current version of jeweler
+    And 'Gemfile' has a development dependency on 'rcov'
+
+  Scenario: bacon
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'bacon'
+
+  Scenario: minitest
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'minitest'
+
+  Scenario: rspec
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Gemfile' has a development dependency on 'rspec'
+
+  Scenario: shoulda
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'shoulda'
+
+  Scenario: micronaut
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'micronaut'
+
+  Scenario: cucumber
+    Given I want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'cucumber'
+
+  Scenario: reek
+    Given I want reek
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'reek'
+
+  Scenario: roodi
+    Given I want roodi
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'roodi'
+
+  Scenario: yard
+    Given I want to use yard instead of rdoc
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'yard'
+
+  Scenario: shindo
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'shindo'